Major upgrades online
Upgrading between major releases is hard, and should be deferred until you have some good reasons and sufficient time to get it right.
You can use replication tools to minimize the downtime required for an upgrade, so we refer to this recipe as an online upgrade.
How to do it…
The following general steps should be followed, allowing at least a month for the complete process to ensure that everything is tested and everybody understands the implications:
- Set up a new release of the software on a new test system.
- Take a standalone backup from the main system and copy it to the test system.
- Test the applications extensively against the new release on the test system.
When everything works and performs correctly, then proceed to the next step.
- Set up a connection pooler to the main database (it may be there already).
- Set up logical replication for all tables from the old to new database servers...
