MIME-Version: 1.0
References: 
 <CAMVgnQ48N4Vspjg-m4TgYEK2-O_F5L0gGEPtjVSMqQrUQ+24Dg@mail.gmail.com>
 <c5b7d760e3aa0af2b0b6f83e36a3acf5bc5ddab6.camel@cybertec.at>
 <6a4bd198.1bd3656d.1df067.50baSMTPIN_ADDED_BROKEN@mx.google.com>
In-Reply-To: <6a4bd198.1bd3656d.1df067.50baSMTPIN_ADDED_BROKEN@mx.google.com>
From: K P Manoj <kpmanojpg@gmail.com>
Date: Tue, 7 Jul 2026 11:27:12 +0530
Message-ID: 
 <CAMVgnQ4oU9aU42HjVL-dj5J8=2dC3kVesb09SDqGCNcTAyjehw@mail.gmail.com>
Subject: Re: PG version 16.14 upgrade went recovery state
To: Michael Banck <mbanck@gmx.net>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000989e9b0655ff116b"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMVgnQ4oU9aU42HjVL-dj5J8%3D2dC3kVesb09SDqGCNcTAyjehw%40mail.gmail.com>
Precedence: bulk

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

Dear Michael,

Thank you for your email.

My primary objective is to mitigate CVE-2026-6473, and the required fix is
only available in version 16.14. Therefore, I will wait for the next minor
release.

Regards,

Manoj K P

On Mon, Jul 6, 2026 at 9:32=E2=80=AFPM Michael Banck <mbanck@gmx.net> wrote=
:

> On Sun, Jul 05, 2026 at 03:06:48PM +0200, Laurenz Albe wrote:
> > On Fri, 2026-07-03 at 15:25 +0530, K P Manoj wrote:
> > > I am encountering an issue when upgrading our PostgreSQL database fro=
m
> minor version 16.10 to 16.14.
> > >
> > > During the upgrade, the database enters an indefinite recovery mode
> across the master, standby,
> > > and multiple cascading replicas. Due to legacy requirements, we are
> utilizing streaming replication
> > > for this setup. Interestingly, when performing the same migration to
> version 16.13, the process
> > > completes successfully without any issues.
> > >
> > > Could you please confirm if there are any known bugs regarding this
> behavior in version 16.14?
> >
> > Yes, this could be bug 19490:
> > https://postgr.es/m/flat/19490-9c59c6a583513b99%40postgresql.org
> >
> > Best wait for 16.15 before updating.
>
> The alternatve is to do a two-step process, where you ugprade everything
> to 16.13, then upgrade the standbys to 16.14. As far as I know, the
> leader needs to be on 16.11 or earlier (while the standbys needs to be
> on 16.4) to hit this bug, so updating it to 16.12 or 16.13 should
> circumvent this as well.
>
> I wrote a blog-post summarizing the issue here:
>
> https://www.credativ.de/en/blog/postgresql-en/replication-deadlock-bug-in=
-current-postgres-releases-14-16/
>
>
> Michael
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>Dear Michael,<br><br>Thank you for y=
our email.<br><br>My primary objective is to mitigate CVE-2026-6473, and th=
e required fix is only available in version 16.14. Therefore, I will wait f=
or the next minor release.<br><br></div><div>Regards,<br><br>Manoj K P</div=
></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr=
" class=3D"gmail_attr">On Mon, Jul 6, 2026 at 9:32=E2=80=AFPM Michael Banck=
 &lt;<a href=3D"mailto:mbanck@gmx.net">mbanck@gmx.net</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, Jul 05, 2026 a=
t 03:06:48PM +0200, Laurenz Albe wrote:<br>
&gt; On Fri, 2026-07-03 at 15:25 +0530, K P Manoj wrote:<br>
&gt; &gt; I am encountering an issue when upgrading our PostgreSQL database=
 from minor version 16.10 to 16.14.<br>
&gt; &gt; <br>
&gt; &gt; During the upgrade, the database enters an indefinite recovery mo=
de across the master, standby,<br>
&gt; &gt; and multiple cascading replicas. Due to legacy requirements, we a=
re utilizing streaming replication<br>
&gt; &gt; for this setup. Interestingly, when performing the same migration=
 to version 16.13, the process<br>
&gt; &gt; completes successfully without any issues.<br>
&gt; &gt; <br>
&gt; &gt; Could you please confirm if there are any known bugs regarding th=
is behavior in version 16.14?<br>
&gt; <br>
&gt; Yes, this could be bug 19490:<br>
&gt; <a href=3D"https://postgr.es/m/flat/19490-9c59c6a583513b99%40postgresq=
l.org" rel=3D"noreferrer" target=3D"_blank">https://postgr.es/m/flat/19490-=
9c59c6a583513b99%40postgresql.org</a><br>
&gt; <br>
&gt; Best wait for 16.15 before updating.<br>
<br>
The alternatve is to do a two-step process, where you ugprade everything<br=
>
to 16.13, then upgrade the standbys to 16.14. As far as I know, the<br>
leader needs to be on 16.11 or earlier (while the standbys needs to be<br>
on 16.4) to hit this bug, so updating it to 16.12 or 16.13 should<br>
circumvent this as well.<br>
<br>
I wrote a blog-post summarizing the issue here:<br>
<a href=3D"https://www.credativ.de/en/blog/postgresql-en/replication-deadlo=
ck-bug-in-current-postgres-releases-14-16/" rel=3D"noreferrer" target=3D"_b=
lank">https://www.credativ.de/en/blog/postgresql-en/replication-deadlock-bu=
g-in-current-postgres-releases-14-16/</a><br>
<br>
<br>
Michael<br>
<br>
<br>
</blockquote></div></div>

--000000000000989e9b0655ff116b--