public inbox for [email protected]  

help / color / mirror / Atom feed

From: K P Manoj <[email protected]>
To: Michael Banck <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: PG version 16.14 upgrade went recovery state
Date: Tue, 7 Jul 2026 11:27:12 +0530
Message-ID: <CAMVgnQ4oU9aU42HjVL-dj5J8=2dC3kVesb09SDqGCNcTAyjehw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAMVgnQ48N4Vspjg-m4TgYEK2-O_F5L0gGEPtjVSMqQrUQ+24Dg@mail.gmail.com>
	<[email protected]>
	<[email protected]>

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 PM Michael Banck <[email protected]> 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 from
> 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-...
>
>
> Michael
>
>
>

view thread (4+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: PG version 16.14 upgrade went recovery state
  In-Reply-To: <CAMVgnQ4oU9aU42HjVL-dj5J8=2dC3kVesb09SDqGCNcTAyjehw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox