| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | sdaekb(at)yandex(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. |
| Date: | 2026-06-16 18:36:29 |
| Message-ID: | ajGU_T_k3yJA3gD5@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2026-Jun-15, Andrey Borodin wrote:
> > On 15 Jun 2026, at 18:39, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> >
> > After rolling back to version 14.22, everything works as intended.
>
> Hi! Thanks for the report. Can you please give a bit more logs? This excerpt is
> missing errors from the startup process. And message from this process could shed
> a light on a root cause.
I suspect e35e466f61b [1] might be related. That's a bug that was
fixed in 2bb60eb4fea [2], just after 14.23.
[1] https://postgr.es/c/e35e466f61b
[2] https://postgr.es/c/2bb60eb4fea
If not, some data from pg_waldump around the problem area might be useful.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"If you have nothing to say, maybe you need just the right tool to help you
not say it." (New York Times, about Microsoft PowerPoint)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-06-16 18:43:12 | Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. |
| Previous Message | Álvaro Herrera | 2026-06-16 18:22:16 | Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change |