MIME-Version: 1.0
References: 
 <GV1P192MB2683BEA93EEC772A22F150C3A50E2@GV1P192MB2683.EURP192.PROD.OUTLOOK.COM>
In-Reply-To: 
 <GV1P192MB2683BEA93EEC772A22F150C3A50E2@GV1P192MB2683.EURP192.PROD.OUTLOOK.COM>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Thu, 21 May 2026 09:43:16 -0400
Message-ID: 
 <CANzqJaA0i41sjsOEYQApoqoap12hMrxiskT3ZGHmMiAiCB-bdw@mail.gmail.com>
Subject: Re: Replica servers hanging after the latest security patch update
To: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000ce1bdb0652541813"
Archived-At: 
 <https://www.postgresql.org/message-id/CANzqJaA0i41sjsOEYQApoqoap12hMrxiskT3ZGHmMiAiCB-bdw%40mail.gmail.com>
Precedence: bulk

--000000000000ce1bdb0652541813
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, May 21, 2026 at 8:58=E2=80=AFAM recep g=C3=BCl <recep_29_@hotmail.c=
om> wrote:

> Hi;
>
> After applying the latest published PostgreSQL security patches, we
> experienced issues on our replicas. We first updated two of our replica
> servers running pg14 and pg15. The replica services were running during t=
he
> binary update. After the binary update was completed, we restarted the
> relevant replica services. Upon observation, we noticed that the replicas
> were waiting at the last checkpointed redo file during the startup phase.
> Meanwhile, although we performed the same operation on our other servers,
> we did not encounter such an issue on those. Has anyone else encountered =
a
> similar problem?
>

1. What *specific* minor version numbers?
2. Did you shut down PG before applying the patches?
3. How did you apply the patches?


--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--000000000000ce1bdb0652541813
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, May 21, 2026 at 8:58=E2=80=AFAM r=
ecep g=C3=BCl &lt;<a href=3D"mailto:recep_29_@hotmail.com">recep_29_@hotmai=
l.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"msg-1083581=
495821888354">


<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Hi;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
=E2=80=82=E2=80=82=E2=80=82=E2=80=82After applying the latest published Pos=
tgreSQL security patches, we experienced issues on our replicas. We first u=
pdated two of our replica servers running pg14 and pg15. The replica servic=
es were running during the binary update. After the binary update
 was completed, we restarted the relevant replica services. Upon observatio=
n, we noticed that the replicas were waiting at the last checkpointed redo =
file during the startup phase. Meanwhile, although we performed the same op=
eration on our other servers, we
 did not encounter such an issue on those. Has anyone else encountered a si=
milar problem?</div></div></div></blockquote><div>=C2=A0</div><div>1. What =
<i>specific</i>=C2=A0minor version numbers?</div><div>2. Did you shut down =
PG before applying the patches?</div><div>3. How did you apply the patches?=
</div></div><div><br clear=3D"all"></div><div><br></div><span class=3D"gmai=
l_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature=
"><div dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&#39=
;t boil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobster!</di=
v></div></div></div></div></div>

--000000000000ce1bdb0652541813--