Manage a Database

Everything here lives in the database’s Settings, and requires the database to be Active — while it’s provisioning, updating, or deleting, changes are temporarily disabled.

Resize compute and storage

Compute (CPU/memory tier) and storage are changed — and saved — independently:

• Scale compute by moving the instance to a larger tier. Reducing resources isn’t supported yet — you can only scale up.
• Grow storage to a larger size. Storage is grow-only, and you can’t select a size below what the instance already uses — so raise it deliberately.

Upgrade the PostgreSQL version

Change the engine version from the General settings when you’re ready to move to a newer major version.

Rotate the admin password

If you’ve lost the admin password — or just want to retire it — use Rotate password on the database’s overview. Rotation is available only while the database is Active.

Rotating generates a new password and shows it once: copy it immediately, it won’t be shown again. The database moves to Updating while the change rolls out — the current password keeps working until the database returns to Active, at which point the new one takes effect.

Delete a database

Deleting lives in the settings Danger Zone, and asks you to type the database’s name to confirm.

Troubleshooting

• Settings are disabled. Changes are blocked while the database is provisioning, updating, or deleting — wait for it to return to Active.
• You can’t pick a smaller tier or storage size. Downsizing isn’t supported: compute only scales up, and storage can’t go below current usage.
• Apps lost database access after a rotation. Update any hand-configured connection details with the new password; linked projects receive it automatically.