Conversation
|
|
||
| We recommend creating a new database instance from a recent backup and upgrading that instance to the desired database version, as you can then switch over to using the new database instance with the new database version at your leisure after making sure no problems cropped up. Drawbacks include having to switch to using a new IP address to connect to the database, though, and any changes made to the original database after the backup was taken will be lost. | ||
| 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 |
There was a problem hiding this comment.
(or use a recently created automatic upgrade) ?
| 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 | ||
| 2. Restore the freshly created backup into a new database instance | ||
| 3. Upgrade the new database instance to your target datastore version |
There was a problem hiding this comment.
Should we always recommend them to use the most recent version?
| for connections, and any changes made to the original database instance after the backup was taken | ||
| will be lost. | ||
|
|
||
| ### Information regarding major database version EOLs |
There was a problem hiding this comment.
Maybe this sections should be specific to PostgreSQL 14. Just ensure that there are no confusion for the users.
| versions that are supported in Pukki. This documentation is important if you are planning to | ||
| do a major version upgrade. | ||
| * [How to migrate a PostgreSQL database to Pukki](../../support/tutorials/pukki_data_migration.md) | ||
| As PostgreSQL 14's end-of-life date is set to arrive on 12th of November, 2026, support for it will be removed from Pukki by then. Users are recommended to upgrade their PostgreSQL 14 instances to PostgreSQL 17 before the EOL date, as restoring database instances from PostgreSQL 14 backups will stop working. |
There was a problem hiding this comment.
-
IMO this warning could be added to all the Pukki pages.
-
Also we could probably add a PostgreSQL 14 EOL to the what is new section.
-
I think repeating ourself is fine when we trying to communicate the PostgreSQL 14 EOL. Maybe it deserves it's own "FAQ" / announcement page
docs/cloud/dbaas/postgresql14eol.md? We could then make sure that all email, warning, "what is new" is pointing to that page. I don't think you should remove anything that you have already written I think we could just "repeat" anyhting on that specific page. What do you think?
2 participants
Proposed changes
https://csc-guide-preview.2.rahtiapp.fi/origin/DBAAS-554/
Checklist before requesting a review