Edit a database

Use Edit Database to give a running database more storage, change who can reach it, attach a different parameter group, or add extensions. You can make several changes at once and save them together.

Before you begin

• A database in the Running state. When the database is in any other state, Edit Database says it can be edited once it is running.
• The update permission for DBaaS in the project. See TIR Access Control.

What you can change

Edit Database has three sections:

• Storage: increase the disk size.
• Network & Security: change the IP allowlist and the VPC. See Control network access to a database.
• Advanced Settings: attach, change or detach the parameter group, and add extensions. See Use parameter groups and Add extensions.

The database’s name, plan, PostgreSQL version and admin username are set when you create it and stay as they are. For a database with a different plan or version, create a new one. See Create a database.

Open Edit Database

1. In the side menu, under Databases, select DBaaS.
2. Choose Edit in the database’s row menu on the Manage Databases list, or in the three-dot menu on its details page. Edit is available only while the database is Running.

While the database is Running, the Overview tab also links straight to the matching section, for example Edit beside IP Allowlist or Parameter Group.

Increase storage

Each storage increase is permanent, so add only what you need.

1. In Storage, the control starts at the current size, marked “(current)”.
2. Move the slider, which goes in steps of 10 GB, or type any whole number of GB. The size can be anything from the current size up to 1,000 GB.
3. Select Update Database.

The database shows Scaling while its disk grows, keeps serving connections, and then shows Running again. After you increase the storage, Price on Overview covers the new size. See pricing.

The disk holds the operating system as well as your data, so less than the full size is free for data. When the disk is 80% full or more, Storage on the Overview tab offers Increase storage.

Save your changes

1. Make the changes you need in any of the sections.
2. Select Update Database, or Cancel to discard your changes.
3. If the change needs a restart, confirm it. The restart drops open connections, and applications need to reconnect once the database is back.

One update applies every change on the page. A change of VPC restarts the database. A change of parameter group also offers Update & Restart. It saves the change and restarts the database, so that settings PostgreSQL reads only at start-up take effect.

When you attach or change a parameter group with Update Database, the settings PostgreSQL reads only at start-up take effect at the next restart. Restart the database when it suits you. See Stop, start and restart a database.

When a change fails to save

If only part of an update is saved, TIR says what was saved and what failed, with the reason for each. The unsaved changes stay on the form, so you can correct them and select Update Database again.

If the whole update fails, TIR gives each reason, under the field it belongs to. Correct the fields and update again.

Storage increases, allowlist changes, parameter group changes and added extensions are recorded on Activity Timeline, for example “IP allowlist updated” or “Parameter group attached”. For help with an update that keeps failing, see Troubleshooting TIR DBaaS.