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 1tFG4N-00C9z3-A0 for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 17:06:47 +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 1tFG4L-008pbj-Cu for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 17:06:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFG4L-008pba-1L for pgsql-general@lists.postgresql.org; Sun, 24 Nov 2024 17:06:45 +0000 Received: from smtp78.iad3a.emailsrvr.com ([173.203.187.78]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFG4I-003YsB-Nj for pgsql-general@postgresql.org; Sun, 24 Nov 2024 17:06:43 +0000 X-Auth-ID: xof@thebuild.com Received: by smtp18.relay.iad3a.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 341C5230E8; Sun, 24 Nov 2024 12:06:41 -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:06:09 -0800 Cc: Ron Johnson , pgsql-general Content-Transfer-Encoding: quoted-printable Message-Id: <1FBD217B-06FE-48CF-AA58-F7ADEDA5ADD2@thebuild.com> 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: 754a9563-a766-45ea-8fe0-cdacb571a0b0-1-1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Nov 24, 2024, at 09:03, Subhash Udata = wrote: > When we shut down the standby, upgrade it, and then start it back up, = will the replication automatically resume from the primary to the = standby? Assuming that the standby has access to any WAL generated during the = shutdown (either still in the primary's WAL directory, or via an archive = using archive_command), yes. If you are not using a WAL archive using = archive_command, you will want to make sure your wal_keep_size parameter = is set high enough that required WAL segments aren't recycled during the = standby's downtime.=