PostgreSQL FAQ

Will DBaaS be ever offered on Cloud Cubes?

As for now, DBaaS is only offered on Virtual Servers. Cloud Cubes may be used in the future as well.

How many connections are available?

Currently, the total limit is 100, with 11 reserved.

Is there a connection pooling option for PosgreSQL?

IONOS DBaaS doesn't provide connection pooling. However, you may use a connection pooler (such as pgbouncer) between your application and the database.

After the connection limit has been reached, will there be an error?

Depending on the library you are using, it should be something like:
failed to create DB connection: addr x.x.x.x:5432: connection refused.

How do we prevent reaching the connection limit?

The best way to manage connections is to have your application maintain a pool of at least 10-20 connections. It is considered bad practice to have a lot of DB connections. However, letting the user configure max_connections themselves in the future is an option.

Can I scale the deployment to increase its connection limit?

Increasing RAM or number of instances does not affect the number of connections available for users. It is also not something support can change.

What are the supported backup methods?

We provide an automated backup within our cloud. If you want to backup to somewhere else, you may use a client-side tool, such as pg_dump.

What are the main considerations for latency and performance?

The number of standby nodes (in addition to the master) doesn’t really matter. If you have one or ten makes no difference. Synchronous modes are slower in write performance due to the increase in latency for communication between master and standby.

Why can't I restore to the time I specified?

If you're receiving an error message Parameter out of bounds: The recovery target time is before the newest basebackup., please check the earliestRecoveryTargetTime of your backup. Your target time of the restore needs to be after this timestamp. Maybe you have another backup for your cluster with an earlier earliestRecoveryTargetTime and can use that.
If the earliestRecoveryTargetTime is missing in your backup, the cluster from where you want to restore wasn't able to do a base backup. This can happen, when you e.g. quickly delete a newly created cluster, since the base backup will be triggered up to a minute after the cluster is available.
Export as PDF
Copy link