| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | sdaekb(at)yandex(dot)ru, PostgreSQL mailing lists <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:43:12 |
| Message-ID: | 416ADEE5-0410-488A-BCFF-C3D8E1D3E6A0@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 16 Jun 2026, at 23:36, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
>
> 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.
Yeah, that was my concern. But that bug manifests as startup process failure.
I've contacted Sergey offlist, he observed hanging
postgres: data: startup recovering 000000060000C29100000016
so it's hard to tell what's going on without backtrace...
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2026-06-17 01:44:05 | RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change |
| Previous Message | Álvaro Herrera | 2026-06-16 18:36:29 | Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. |