PostgreSQL is an open source, object-relational database built with extensibility, data integrity, and speed in mind. Its concurrency support makes it fully ACID compliant, and it supports dynamic loading and catalog-driven operations to let users customize its data types, functions, and more.
There are two kinds of database cluster plans you can choose from: single node clusters and high availability clusters.
Single node clusters begin at $15/month for a single node cluster with 1GB of RAM. Single node clusters are not highly available, but they feature automatic failover. These clusters are a good fit for preliminary development and testing.
High availability clusters begin at $50/month ($0.074/hour) for the 2GB RAM/2 vCPU plan when you add at least one matching standby node for automatic failover.
You can add or remove standby nodes at any time. Other features, like point-in-time recovery and read-only nodes, vary by database engine. Learn more about feature availability..
Inbound data transfer is included in the price of the cluster. Outbound data transfer billing is waived until January 1, 2020, at which time it will be billed at $0.01/GB.
PostgreSQL database clusters are in General Availability. Our regional availability matrix has more detail about our datacenter regions and product availability. Managed databases will not be offered in NYC2, AMS2, or SFO1.
Automatic updates. You can select a date and time during which weekly automatic updates for the database engine and operating system will occur to keep the service stable and secure.
Daily point-in-time backups. Databases are automatically backed up every day, which lets you restore data to any point within the previous seven days.
High availability with automated failover. In the event of a failure, managed databases with a standby node will automatically switch data handling to the standby node to prevent unplanned downtime. Learn more about high availability for managed databases.
End-to-end security. Data is encrypted at rest with LUKS and in transit with SSL.
Cluster metrics and alerting. Cluster metrics visualizations help you monitor the performance of the nodes in a database cluster, like resource usage, to guide capacity planning and optimization. Alert policies notify you when a metric rises above or falls below a threshold you set, like high CPU or low memory.
Read-only nodes. You can add read-only nodes in geographically disparate data centers.
Database metrics and query insights. PostgreSQL-specific performance metrics help you assess the health of the database, pinpoint performance bottlenecks, and identify unusual use patterns that may indicate an application bug or security breach.
PostgreSQL database metrics include number of database connections, cache hit ratio, deadlock creation rate, and fetch, insert, delete, and update throughput.
By default, you are limited to 3 clusters per account or team.
Each cluster is limited to 5 read-only nodes.
You cannot delete the default database and user.
When you restore from a backup, you must restore to a new node and re-add any read-only or standby nodes. See How to Restore from Backups for details.
Point-in-time-recovery (PITR) is limited to the last 7 days.
Private networking is available within the same account or team only and within the same datacenter region only.
You cannot resize cluster nodes to smaller sizes. To move from a bigger node to a smaller node, create a new cluster with the desired node size and import your data.
You cannot currently add DigitalOcean Cloud Firewalls to a database cluster’s trusted sources.
We support only PostgreSQL v10 and v11.
We support only selected PostgreSQL extensions. See Supported PostgreSQL Extensions for a comprehensive list.
Each PostgreSQL cluster allows 25 backend connections per 1 GB of RAM minus 3 connections per node that are reserved for maintenance.
|Plan Size||Available Backend Connections|
|1 GB RAM||22|
|4 GB RAM||97|
|8 GB RAM||197|
|16 GB RAM||397|
|32 GB RAM||797|
|64 GB RAM||1,597|
We support connection pooling, backed by PgBouncer, to increase the number of available concurrent client connections.
In order to maintain cluster stability, users cannot access the
You must use a third-party client to manage access control lists (ACLs). You can add users and databases from the DigitalOcean Control Panel.
You can’t use DigitalOcean’s Cloud Firewalls with managed databases. Until support is available, you can restrict access to nodes by their incoming IPv4 addresses.
Point-in-time-recovery (PITR) operations are limited to the last 7 days. The date picker doesn’t restrict you from choosing an earlier date; you will receive an error if you try to recover from a date outside of the 7-day window.