In this post we'll set up a 3-node EDB Postgres Distributed (PGD) cluster running community Postgres 16. Then we'll upgrade the entire cluster in place from Postgres 16 to Postgres 17. We'll demonstrate that even while bringing individual nodes down for the major version upgrade, the cluster overall will remain available for reads and writes. There may be nuances to your particular environment (additional extensions, permissions, etc.) that I'm ignoring in this post to focus on the simple and happy path. I'm demonstrating this on a fresh Debian 12 machine. Grab Postgres 16 First we follow the
↧
