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.

Is there a connection pooling option for PosgreSQL?

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

To use our managed pgbouncer see Activate a PostgreSQL Connection Pooler.

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 not considered a good 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?

Yes. For more information, see Connection Limits.

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.

Which replication modes are supported for PostgreSQL clusters?

PostgreSQL supports only ASYNCHRONOUS and STRICTLY_SYNCHRONOUS replication modes. Existing clusters using SYNCHRONOUS mode can switch to one of these supported replication modes using the API.

What are the main considerations for latency and performance?

The number of standby nodes (in addition to primary node) 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 a primary node and a standby node.

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

If you are receiving an error message Parameter out of bounds: The recovery target time is before the newest basebackup., check the earliestRecoveryTargetTime of your backup. Your target time of the restore needs to be after this timestamp. You can use an earlier earliestRecoveryTargetTime backup for your cluster if you have one.

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 quickly delete a newly created cluster, since the base backup will be triggered up to a minute after the cluster is available.

Which metrics are available for PostgreSQL?

Cluster metrics include connections count, CPU utilization, disk Input/Output (I/O) time, instance count, memory usage and availability, Linux load average, disk space, index scans, and sequential scans. For more information, see Metrics Overview. You can view the detailed performance metrics using the Telemetry API.