Update a PostgreSQL Managed Database

Make changes to an existing PostgreSQL Managed Database.

• The user needs read_write user grant access to the database.

• The database's status needs to be active.

• New values set in the allow_list overwrite existing values. To keep existing values, run the List PostgreSQL Managed Databases operation, store the allow_list addresses from the response, and include them with any new addresses in this operation.

• Updates to your allow_list may take a short period of time to complete, making this operation inappropriate for rapid successive updates.

• Also allows resizing the database cluster to a larger one. Clusters can't be resized to smaller plans.

• All Managed Databases include automatic updates, which apply security patches to the underlying operating system of the Managed PostgreSQL Database. Use the updates object in this operation to modify the maintenance window for these updates.

• If your database cluster is configured with a single node, downtime occurs during maintenance updates. Use the updates object to adjust the window to match a time that's the least disruptive to your application and users. Also consider upgrading to a high availability plan to avoid any maintenance downtime.

• Major upgrades are optional until the service reaches end of service, and can be done in place.

• You can't update engine_config advanced parameter settings for a suspended database. You'll need to resume it first.

• A successful request triggers a database_update event.

• Beta. You can update an existing PostgreSQL Managed Database to move it to a Virtual Private Cloud (VPC) using the private_network object in the request. This support is in beta. Talk to your Akamai account team for more details.

  📘

  Currently, VPC subnets associated with Managed Database instances don't automatically block outbound connections outside the subnet. To limit network exposure, you should configure Cloud Firewall rules to explicitly deny outbound connections beyond the intended subnet. For more details on configuring rules, see the Cloud Firewall documentation.

​

linode-cli databases postgresql-update 123 \
  --label example-db \
  --allow_list 203.0.113.1 \
  --allow_list 192.0.1.0/24 \
  --type g6-standard-1 \
  --updates.frequency weekly \
  --updates.duration 3 \
  --updates.hour_of_day 12 \
  --updates.day_of_week 4 \

<https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-the-linode-cli>

databases:read_write

<https://techdocs.akamai.com/linode-api/reference/get-started#oauth>