2 ms·

Upgrading from v11 to v16 is not materially different in Postgres from v14 to v16. Same tools. Same strategies.

• enraged_camel 2y ago
  We are planning to upgrade from 11 to 17 soon. Even thinking about it is giving me ulcers. Our infra provider said we actually need to upgrade to 13 first, and then to 17. They did not provide a reason.
  • Tostino 2y ago
    I went through a postgres 10 > 16 upgrade recently. What made it easier was just doing a test run of the upgrade process. Did a restore to a stage environment, worked on my upgrade scripts until I was happy (deployed to VMs with ansible, so manual work to write the upgradeprocessfor me), restored again and ran the upgrade process fresh, and then tested my application, backup scripts, restores, etc. Had everything working entirely smoothly multiple times before pulling the trigger in production. No stress at all when we did it in prod.
    • ttfkam 2y ago
      Yep, that was our strategy as well: just keep iterating until the script run cleanly from start to finish without errors.
  • fillest 2y ago
    A personal warning about 17.0 if you use streaming replication: secondary replica leaks memory quite actively. 16.4 is OK.