Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Subject: Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23,
 the database goes into an infinite loop.
From: Andrey Borodin <x4mmm@yandex-team.ru>
In-Reply-To: <ajGU_T_k3yJA3gD5@alvherre.pgsql>
Date: Tue, 16 Jun 2026 23:43:12 +0500
Cc: sdaekb@yandex.ru,
 PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <416ADEE5-0410-488A-BCFF-C3D8E1D3E6A0@yandex-team.ru>
References: <ajGU_T_k3yJA3gD5@alvherre.pgsql>
To: =?utf-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>
Archived-At: 
 <https://www.postgresql.org/message-id/416ADEE5-0410-488A-BCFF-C3D8E1D3E6A0%40yandex-team.ru>
Precedence: bulk


> On 16 Jun 2026, at 23:36, =C3=81lvaro Herrera <alvherre@kurilemu.de> =
wrote:
>=20
> On 2026-Jun-15, Andrey Borodin wrote:
>=20
>>> On 15 Jun 2026, at 18:39, PG Bug reporting form =
<noreply@postgresql.org> wrote:
>>>=20
>>> After rolling back to version 14.22, everything works as intended.
>>=20
>> 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.
>=20
> I suspect e35e466f61b [1] might be related.  That's a bug that was
> fixed in 2bb60eb4fea [2], just after 14.23.
>=20
> [1] https://postgr.es/c/e35e466f61b
> [2] https://postgr.es/c/2bb60eb4fea
>=20
> 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.=