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 <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 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.
