Managing a 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.
Manage an OCI Database with PostgreSQL database system using the following tasks:
- Creating a Database System
- Creating a Database System from a Backup
- Listing Database Systems
- Getting Details About a Database System
- Connecting to a Database
- Editing a Database System
- Editing the Management Policy of a Database System
- Changing the Configuration Applied to a Database System
- Enabling Extensions for a Database
- Updating the Performance Tier of a Database System
- Changing the Shape or Hardware Configuration of a Database System
- Updating the Network Security Group of a Database System
- Managing the Administrator Credentials for a Database System
- Tagging a Database System
- Moving a Database System to Another Compartment
- Deleting a Database System
- Managing OCI Database with PostgreSQL Configurations
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 tenancyFor more information, see OCI Database with PostgreSQL Policies.