From: | Christophe Pettus <xof(at)thebuild(dot)com> |
---|---|
To: | Subhash Udata <subhashudata(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication |
Date: | 2024-11-24 17:04:03 |
Message-ID: | B252D4B3-C9E2-4C19-93FC-DB4E8FD23B41@thebuild.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Nov 24, 2024, at 08:51, Subhash Udata <subhashudata(at)gmail(dot)com> wrote:
> However, my concern lies in the fact that we are working with production servers, where downtime is not acceptable.
There is no way to upgrade community PostgreSQL, either to a new minor version or a new major version, with absolute zero downtime.
To do a minor version upgrade such as this, the only thing that is required is to restart the server with the new binaries. While this does require a service interruption, it's quite short, and is not significantly longer than the interruption required to do a failover. You can do the primary and secondary in either order, although upgrading the primary first is probably the safest route. You don't have to switch the primary / secondary roles in this case, nor rebuild the secondary server using pg_basebackup.
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2024-11-24 17:06:09 | Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication |
Previous Message | Subhash Udata | 2024-11-24 17:03:58 | Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication |