| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | K P Manoj <kpmanojpg(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: PG version 16.14 upgrade went recovery state |
| Date: | 2026-07-05 13:06:48 |
| Message-ID: | c5b7d760e3aa0af2b0b6f83e36a3acf5bc5ddab6.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mahesh Sathe | 2026-07-06 10:36:13 | Re: Major upgrade in patroni cluster |
| Previous Message | K P Manoj | 2026-07-03 09:55:35 | PG version 16.14 upgrade went recovery state |