Managing OCI Database with PostgreSQL Database System

Manage an OCI Database with PostgreSQL database system.

A OCI Database with PostgreSQL database system consists of one or more Compute instances with an OS, a managed PostgreSQL server, a Virtual Network Interface Card (VNIC), and storage.

You can perform the following database system tasks:

Display a list of the database systems.

Create a database system.

Create a database system from a backup.

View the details of a database system.

Update a database system's settings.

Enable or disable a database system's reader endpoint.

Update the database system's management policy.

Change the database system's configuration.

Enable the extensions for a database system.

Update a system database's performance tier.

Change a database system's shape and hardware setup.

Update a database system's Network Security Group settings.

Manage a database system's administrative credentials.

Move a database system to a different compartment.

Delete a database system from the compartment.

Limitations and Considerations

In addition to service resource limits, the following limitations apply to database systems:

  • Maximum storage per database system: 32 TB
  • Maximum read replica nodes per database: 7
  • Database systems can only be created in subnets that don't have IPv6 enabled.

Required IAM Policy

The following policy statements allow a group of administrators to manage OCI Database with PostgreSQL database systems:

Allow group <postgresql-admin-group> to read compartments in tenancy
Allow group <postgresql-admin-group> to manage postgres-db-systems in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to manage postgres-backups in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to read postgres-work-requests in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to manage postgres-configuration in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to manage virtual-network-family in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to read secret-family in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to read vaults in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to read metrics in [ tenancy | compartment <compartment_name> | compartment id <compartment_OCID> ]
Allow group <postgresql-admin-group> to use tag-namespaces in tenancy

For more information, see OCI Database with PostgreSQL Policies.