This page provides the technical capabilities and limitations of the Managed Databases (also called 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 13
- PostgreSQL 14
- PostgreSQL 15
- PostgreSQL 16
Please refer to our Cloud Databases - 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
Three plans are available:
- Essential
- Business
- Enterprise
Here is an overview of the various plans' capabilities:
| Plan | Number of nodes (by default) | Read replicas |
|---|---|---|
| Essential | 1 | No |
| Business | 2 | Planned |
| Enterprise | 3 | Planned |
Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterward.
Nodes and replicas
- Essential: the cluster can support at most one node.
- Business: the cluster is delivered with 2 nodes by default. Adding read replicas is planned.
- Enterprise: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
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
Here are the node types you can choose from:
| Name | Storage | vCores | Memory (GB) |
|---|---|---|---|
| db1-4 | From 80 GB to 240 GB | 2 | 4 |
| db1-7 | From 160 GB to 480 GB | 2 | 7 |
| db1-15 | From 320 GB to 960 GB | 4 | 15 |
| db1-30 | From 640 GB to 1.92 TB | 8 | 30 |
| db1-60 | From 1.28 TB to 3.84 TB | 16 | 60 |
| db1-120 | From 2.56 TB to 7.68 TB | 32 | 120 |
Right now, all nodes of a given cluster should be of the same type and distributed in the same region.
Flexible storage
You can increase the storage of your cluster up to the maximum allowed for a given reference. Please refer to the Cloud Databases - Resize Your Cluster 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:
- When reaching a concerning level of disk usage, a warning email is sent.
- 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.
- You then can 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 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 subnets 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 to a maximum of 1000 active connections.
So for example on a server with 7 GB memory, you will get approximately 200 connections, and with 15 GB 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 Control Panel and the API. Additionally, cross-service integration can be configured to leverage your logs and metrics in other Cloud Database services. You could then view your PostgreSQL logs in OpenSearch and metrics in Grafana. See the Cross Service Integration documentation for more information.
- 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.
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.