Skip to main content

PostgreSQL® - Capabilities and limitations

Stephanie R.
Updated

This page provides the technical capabilities and limitations of the Cloud Databases for PostgreSQL® offer.

We continuously improve our offers. You can follow and submit ideas to add to our roadmap.

 

Capabilities and limitations

Supported regions

To view Cloud Databases' availability, please see our regions and availability webpage.

Entire database instances have to be in the same region.

 

PostgreSQL® versions

The Cloud Databases offer supports the following PostgreSQL® versions:

  • PostgreSQL® 14
  • PostgreSQL® 15
  • PostgreSQL® 16
  • PostgreSQL® 17
  • PostgreSQL® 18

Please refer to our Lifecycle Policy for recommendations on version upgrades and end-of-life announcements of major versions. Additionally, you can follow the EOL lifecycle for the PostgreSQL® version on their official page.

 

PostgreSQL® connectors

You can use any of the PostgreSQL®-recommended drivers and extensions to access your instance.

 

Plans

The available plans are:

  • Essential: 1 node
  • Business: 2 nodes
  • Enterprise: 3 nodes

Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features, such as backup retention.

 

License type

PostgreSQL® software is under the PostgreSQL® License, a liberal open-source license, similar to BSD or MIT licenses. More information can be found here.

 

Hardware resources

For information on node types and pricing, please refer to our pricing page.

 

Flexible storage

You can increase the storage of your cluster up to the maximum allowed for a given reference. Please refer to the Resize your service storage guide for more information.

 

Node template upgrade

You can upgrade the node template of your cluster to scale your hardware resources up. This operation causes no interruption of service, but be aware that you will not be able to downgrade the node template afterwards.

 

Disk type

The type of storage available may vary according to the region your cluster lives in: see Availability of Public Cloud products for more information about block storage type availability depending on the region. Thus, your cluster may be backed by, e.g., High Speed or High Speed Gen2 block storage.

Also, the performance characteristics of the various storage offerings may vary depending on, e.g., the storage size your cluster uses: High Speed may offer better IOPS than High Speed Gen2 for some disk sizes. See our Block Storage webpage for more information about those performance characteristics.

Cloud Databases will select your cluster's most efficient disk type depending on your cluster parameters.

 

Effective storage

The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.

We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:

  1. When reaching a concerning level of disk usage, a warning email is sent.
  2. When reaching a concerning level of disk usage, the service is moved to the "DISK_FULL" state, and "read-only" mode, meaning no more writes can be done.
  3. You can then upgrade to a higher service plan with more storage.

See the Handling «Disk Full» situations documentation for more information.

 

Features

Network

PostgreSQL® clusters are reachable through the port defined in the OVHcloud Control Panel.

Public as well as private networking (vRack) can be used for all the offers.

Ingress and Egress traffic are included in the service plans and are unmetered.

The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.

Private network considerations

Here are some considerations to take into account when using a private network:

  • Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g., you won’t be able to delete the network if you didn’t stop the Cloud Databases services first.
  • When connecting from an outside subnet, the OpenStack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
  • Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
  • OpenStack subnet routes announcement will not be applied to your services.
  • You can only create private network services if you are the original owner of the network. You cannot create private network services on a shared network.
Authorized IPs

Once your service is up and running, you will be able to specify CIDR blocks to authorize incoming traffic. Until then, your service will be unreachable.

 

Maximum simultaneous connections

The number of simultaneous connections in Cloud Databases for PostgreSQL® depends on the available total memory on the node. We allow approximately 100 connections per 4 GB of RAM, capped at a maximum of 1000 active connections.

So, for example, on a server with 7 GB of memory, you will get approximately 200 connections, and with 15 GB of memory, you will get 400 connections.

 

Advanced parameters

You can further customize your PostgreSQL® by using advanced parameters. See the Advanced parameters references documentation for more information on the supported parameters.

 

Backups

Essential plan clusters are automatically backed up daily during their maintenance window. Backup retention is 2 days.

Business plan clusters are automatically backed up daily during their maintenance window. Backup retention is 14 days.

Enterprise plan clusters are automatically backed up daily during their maintenance window. Backup retention is 30 days.

See the Automated backups guide for more information.

 

Logs and metrics

Logs and metrics are available through the OVHcloud Control Panel and OVHcloud API, and can be forwarded to Logs Data Platform. For setup instructions, see our How to set up logs forwarding guide.

  • Logs retention: 1000 lines of logs
  • Metrics retention: 1 calendar month

Please note that if the database instance is deleted, logs and metrics are also automatically deleted.

 

Users and roles

Creation of users is allowed via the Control Panel and API with default admin roles and privileges. The only specific privilege you can set is replication.

 

Data encryption

For detailed information about encryption, see our Security Overview guide.

 

Go further

For more information and tutorials, please see our other Managed Databases & Analytics or Platform as a Service guides. You can also explore the guides for other OVHcloud products and services.

OVHcloud Managed Databases and Analytics:

  • Grafana® is a registered trademark of Grafana Labs and is used with the permission of Grafana Labs. OVH SAS and its subsidiaries are not affiliated with or endorsed by Grafana Labs.
  • Kafka® is a registered trademark of The Apache Software Foundation and has been licensed for use by OVHcloud, who has no affiliation with and is not endorsed by The Apache Software Foundation.
  • MongoDB® is a registered trademark of MongoDB, Inc.
  • MySQL® is a registered trademark of Oracle and/or its affiliates.
  • PostgreSQL® is a registered trademark of the PostgreSQL Community Association of Canada.

Related articles