For the complete documentation index, see llms.txt. This page is also available as Markdown.

Update a PostgreSQL Cluster

After creation, you can modify the name, properties, configuration details, upgrade the cluster version, and the maintenance period of a PostgreSQL cluster.

To modify a cluster, follow these steps:

1

1. In the DCD, go to Menu > Databases > PostgreSQL.

A list of all PostgreSQL clusters is displayed.

2. Click Edit in the OPTIONS column for the cluster you want to modify.

Select Edit

Note: Alternatively, you can click the cluster name or select Details in the OPTIONS column to open the cluster details page, and then click Edit.

Alternative edit option
2

Modify cluster properties

In the Properties section, you can update the following:

1. Cluster Name: Enter an updated name for the cluster. The name can contain a maximum of 63 characters, including letters, numbers, spaces, slashes, dashes, underscores, and dots.

3

Update the cluster configuration

In the Cluster configuration section, you can update the following:

1. PostgreSQL Version: Select a PostgreSQL version from the drop-down list. You can only upgrade to a higher version; downgrades are not supported.

2. Instances: Enter the number of instances for the cluster. We recommend a minimum of 3 instances for production usage.

3. Synchronization mode: Select the replication mode from the drop-down list:

  • Asynchronous: Transactions are committed without waiting for replicas to confirm. Offers better performance but may result in a small amount of data loss during failover.

  • Synchronous: Each transaction waits for confirmation from at least one replica before committing. Ensures no data loss on failover at the cost of some latency.

4. Connection pooler: Select the connection pooler mode from the drop-down list to manage client connections to the database. Select Disabled if connection pooling is not required.

5. Backup retention (days): Enter the number of days backups are retained. The valid range is 1–365 days.

4

Adjust instance resources

In the Instance configuration section, adjust the resources allocated per instance:

1. Number of CPUs (per instance): Use the slider to set the number of CPU cores per instance.

2. RAM Size (per instance): Use the slider to set the amount of RAM per instance.

3. Storage Size: Enter the storage size in GB. For optimal performance, we recommend setting the storage size to 100 GB.

Note: The Current availability panel on the right displays the total resources currently in use and the limits available in your contract for CPU, RAM, and storage.

Note: PostgreSQL v2 clusters use SSD Premium storage exclusively. HDD and SSD Standard storage types available in v1 are not supported in v2.

5

Review network configuration

The Network configuration section displays the network settings configured during cluster creation.

Note: These settings are read-only and cannot be changed after the cluster is created.

  • Virtual Data Center: The data center to which the cluster is connected.

  • VDC LAN: The LAN within the data center used for cluster connectivity.

  • IP/Subnet: The private IP address and subnet assigned to the cluster.

6

Update the maintenance window

In the Maintenance period (optional) section, you can update the following:

1. Day: Select a day of the week from the drop-down list.

2. Start Time (UTC): Enter or select a time using the pre-defined format (hh:mm). The maintenance window covers a 4-hour period from the selected start time.

Note: If no maintenance period is specified, maintenance can occur any time from Monday to Friday, 7 AM–5 PM.

7

Modify Observability settings

In the Observability section, you can update the following:

1. Enable logs: Turn-on to forward cluster logs to your logging endpoint.

2. Enable metrics: Turn-on to forward cluster metrics to your monitoring endpoint.

Note: Observability services must be activated for your contract before logs and metrics can be collected. If not activated, selecting these settings is accepted but has no effect. To activate the Observability service, see Central Logging and Central Monitoring.

8

Save the changes

Review the Estimated costs displayed at the bottom of the page, then click Save to apply your changes.

Update a PostgreSQL cluster

Next steps

Last updated

Was this helpful?