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 1tFGDu-00CAce-BC for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 17:16:38 +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 1tFGDs-008wvB-TM for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 17:16:36 +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 1tFGDs-008wv1-I3 for pgsql-general@lists.postgresql.org; Sun, 24 Nov 2024 17:16:36 +0000 Received: from mail-pf1-x432.google.com ([2607:f8b0:4864:20::432]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFGDq-003YwE-4E for pgsql-general@postgresql.org; Sun, 24 Nov 2024 17:16:35 +0000 Received: by mail-pf1-x432.google.com with SMTP id d2e1a72fcca58-724d23df764so2653266b3a.1 for ; Sun, 24 Nov 2024 09:16:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732468593; x=1733073393; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iQ1T7FfE4ljo0/TcNCr7WswwqvapL/+6dyme8Bt/7XE=; b=hI5pUOGqxGPI4DAKy6tPWrZr6yVRkv92CD5ova5pt1kGRjQhhmvmivV58wTARyiE5J gix9lKaPerEcDnpuvU7b9NX5p8uSmX/h4kYdx+CoYwUdoVbWJTFiKMbgC70N4vNpxcnv L5dsn6H0XunilwDaSRuqo8NB/+ICjAyDeWNxKXITk5WcnWt00ANhWSnt9cAYDFRDfUsW Q8uB2s7g1TCr5Ao4ojWNX01Y3k/olwsKB289AGNfzmKbJRQm82cvadxmmsZL0DANODdA 14wYwnOhZrfVXdANkIzX/AgEpnm6Ts/BGfRy7fgl+z9dxYeXK1qSJ2UoR2TLsDE3vWPc +mgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732468593; x=1733073393; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iQ1T7FfE4ljo0/TcNCr7WswwqvapL/+6dyme8Bt/7XE=; b=aCl8bNQLAJ1aq7zOGoS9S+ccRIrumWYqqNEIkHsrFCmicEQR+ZeWHDQGrdOOHn97YU WOHtc5SxQY3EiYudJX5M5Z/42ruexlfxWIGPYYYGYTUCD+DdvUz+6sAcIDoXY3EwIpl1 BxgTxizpRtftWIHx09AZ26xwsvNZYK1Bv+39lUpaT3V8YDGoy4KpMi69wn1Q+MUBtwp0 /hUQHgJ/QRlCbnMjWN1oTu6uTn80HzHQVvuYVI9lXq33A3HtMSmTIMBcqpXKlAW7FD0l eEJpnb9dOoD7Ssgb/pUNy2Gi7Wy5fc4rLNgMb3nQFP69EU5sgk8Wo4fcrSCAX5C6RYK4 KJEQ== X-Forwarded-Encrypted: i=1; AJvYcCX0BxbO5Ucl3YSpyo0aN3dhtqkwgAYs/jUutpXT6LOsF+hRf3Q/DcTu4Hkfe5c0K8wYfE9YMlLYwtO386+E@postgresql.org X-Gm-Message-State: AOJu0YyVP7200xHB1rj7pzVmeLh+jZi+8fYhE8Uo3HR/Lfh/Jj0D+v+j OtmyrWuG8vWAR99TTYsmpQyxd1TgGSJxqJTugYCXGeQhBPWC5LjzVYIXCpXSr4+GjBWmmjmE4ZK yaey65j67OUGnzLr1P7xybnrHxug= X-Gm-Gg: ASbGncvwhN7+iN2TmdWNkqIp8Aq/jI2LlQ3CSh/+tUXQ8fBZ2pA1PHTIqGeRiGuyGZ3 j09G5OiE5v2i0ADzwq63VhYArDDHKIg== X-Google-Smtp-Source: AGHT+IHPHtv3Gf0ZkUqfuYPCDuqnwdDrkf8/LevWpMiNjwiJFdd3Oy7bCvzUVvd+Pjj2yRQR80aO95fuH58bYoirIHw= X-Received: by 2002:a17:903:94c:b0:212:77d:3899 with SMTP id d9443c01a7336-2129f240e13mr184080205ad.31.1732468592896; Sun, 24 Nov 2024 09:16:32 -0800 (PST) MIME-Version: 1.0 References: <6c498f0e-64f9-449a-9b90-5cd72d00e2ef@aklaver.com> <2a7d96ac-83a7-4ddc-a3ce-9c637f2c1c76@aklaver.com> <1FBD217B-06FE-48CF-AA58-F7ADEDA5ADD2@thebuild.com> In-Reply-To: <1FBD217B-06FE-48CF-AA58-F7ADEDA5ADD2@thebuild.com> From: Subhash Udata Date: Sun, 24 Nov 2024 22:46:21 +0530 Message-ID: Subject: Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication To: Christophe Pettus , Adrian Klaver Cc: Ron Johnson , pgsql-general Content-Type: multipart/alternative; boundary="0000000000001073480627abc7b4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001073480627abc7b4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you, everyone, for your valuable clarifications and insights. Your guidance has been incredibly helpful in addressing my concerns and understanding the best approach to proceed. I truly appreciate the time and effort you=E2=80=99ve taken to assist me. On Sun, 24 Nov 2024 at 22:36, Christophe Pettus wrote: > > > > 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. --0000000000001073480627abc7b4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Thank you, everyone, for your valuable clarifications a= nd insights. Your guidance has been incredibly helpful in addressing my con= cerns and understanding the best approach to proceed.

I truly appreci= ate the time and effort you=E2=80=99ve taken to assist me.


On Sun, 24 No= v 2024 at 22:36, Christophe Pettus <= xof@thebuild.com> wrote:


> On Nov 24, 2024, at 09:03, Subhash Udata <subhashudata@gmail.com> 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?<= br>
Assuming that the standby has access to any WAL generated during the shutdo= wn (either still in the primary's WAL directory, or via an archive usin= g archive_command), yes.=C2=A0 If you are not using a WAL archive using arc= hive_command, you will want to make sure your wal_keep_size parameter is se= t high enough that required WAL segments aren't recycled during the sta= ndby's downtime.
--0000000000001073480627abc7b4--