Skip to content

Dbaas 624 #2993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joonas-somero merged 3 commits into from
May 11, 2026
Merged

Dbaas 624 #2993

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
70138af
Add upgrade instructions to the eol page
csc-kivinenv May 7, 2026
69894a6
Use info box instead
csc-kivinenv May 7, 2026
9848ed6
Merge branch 'master' into DBAAS-624
joonas-somero May 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion docs/cloud/dbaas/postgres-14-eol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,21 @@ On the end-of-life date, 2026-11-12:

## What actions should I take?

Our recommendation is for users with PostgreSQL 14 instances to upgrade them to PostgreSQL 17 well before the end-of-life date. This way you have control over the resulting downtime, and can make sure everything that depends on the database continues to function as before. Instructions for performing the upgrade can be found on the [database operations page here](operations.md), and some information regarding PostgreSQL versions on the [PostgreSQL versions page here](postgres-versions.md).
Our recommendation is for users with PostgreSQL 14 instances to upgrade them to PostgreSQL 17 well before the end-of-life date. This way you have control over the resulting downtime, and can make sure everything that depends on the database continues to function as before. Instructions for performing the upgrade can be found below this paragraph or on the [database operations page here](operations.md), and some information regarding PostgreSQL versions on the [PostgreSQL versions page here](postgres-versions.md).

!!! info "Our recommended procedure for major version upgrades:"

0. Reserve plenty of time for the upgrade process and familiarize yourself with any changes between the database versions
1. Create a new backup of the database instance (or use the most recent automatic backup)
2. Restore the freshly created backup into a new database instance
3. Upgrade the new database instance to your target datastore version (we recommend using the most recent version available)
4. Test that connections to the new instance work as expected and that your data looks correct

After this, you can either move to use the new instance and delete the original one, or continue with
upgrading the original instance and deleting the new one.
Drawbacks with changing to the new instance include having to switch to use the new IP address
for connections, and any changes made to the original database instance after the backup was taken
will be lost.

Any PostgreSQL 14 instances not upgraded to 17 by the end-of-life date will be upgraded by Pukki admins. This will result in some unscheduled downtime for the database instance, and we have no way of checking that any database connections recover afterwards.

Expand Down