Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFG2J-00C9qz-VJ for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 17:04:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tFG2I-008mMP-Ks for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 17:04:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFG2I-008mMF-9c for pgsql-general@lists.postgresql.org; Sun, 24 Nov 2024 17:04:38 +0000 Received: from smtp72.iad3a.emailsrvr.com ([173.203.187.72]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFG2G-003cs8-96 for pgsql-general@postgresql.org; Sun, 24 Nov 2024 17:04:37 +0000 X-Auth-ID: xof@thebuild.com Received: by smtp10.relay.iad3a.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 261E2633C; Sun, 24 Nov 2024 12:04:34 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication From: Christophe Pettus In-Reply-To: Date: Sun, 24 Nov 2024 09:04:03 -0800 Cc: Adrian Klaver , pgsql-general@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <6c498f0e-64f9-449a-9b90-5cd72d00e2ef@aklaver.com> <2a7d96ac-83a7-4ddc-a3ce-9c637f2c1c76@aklaver.com> To: Subhash Udata X-Mailer: Apple Mail (2.3776.700.51) X-Classification-ID: fc4a7d9c-6deb-4db2-8a67-7a73e34ca427-1-1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Nov 24, 2024, at 08:51, Subhash Udata = 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.=