> On 16 Jun 2026, at 23:36, Álvaro Herrera <alvherre@kurilemu.de> wrote:
>
> On 2026-Jun-15, Andrey Borodin wrote:
>
>>> On 15 Jun 2026, at 18:39, PG Bug reporting form <noreply@postgresql.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.
