public inbox for [email protected]
help / color / mirror / Atom feedBUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
7+ messages / 5 participants
[nested] [flat]
* BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
@ 2026-06-15 13:39 PG Bug reporting form <[email protected]>
2026-06-15 17:44 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: PG Bug reporting form @ 2026-06-15 13:39 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
The following bug has been logged on the website:
Bug reference: 19521
Logged by: Sergey Apoychenko
Email address: [email protected]
PostgreSQL version: 14.23
Operating system: CentOS 7.9
Description:
After a minor PostgreSQL update from 14.22 to 14.23 on a physical replica,
endless messages appear.
When starting the database
2026-06-15 15:17:27.331 [2582] [email protected](58784) /postgres/
[unknown] |6a2fed57.a16|:2 (0): > DETAIL: Consistent recovery state has not
been yet reached.
2026-06-15 15:17:28.543 [2584] [email protected](58788) /postgres/
[unknown] |6a2fed58.a18|:1 (0): > FATAL: the database system is not yet
accepting connections
2026-06-15 15:17:28.543 [2584] [email protected](58788) /postgres/
[unknown] |6a2fed58.a18|:2 (0): > DETAIL: Consistent recovery state has not
been yet reached.
2026-06-15 15:17:29.736 [2586] [email protected](58792) /postgres/
[unknown] |6a2fed59.a1a|:1 (0): > FATAL: the database system is not yet
accepting connections
2026-06-15 15:17:29.736 [2586] [email protected](58792) /postgres/
[unknown] |6a2fed59.a1a|:2 (0): > DETAIL: Consistent recovery state has not
been yet reached.
2026-06-15 15:17:32.329 [2589] [email protected](58796) /postgres/
[unknown] |6a2fed5c.a1d|:1 (0): > FATAL: the database system is not yet
accepting connections
When trying to stop the database
2026-06-15 15:20:33.445 [1803] @ // |6a2fec4a.70b|:7 (0): > LOG: received
fast shutdown request
2026-06-15 15:20:33.588 [3269] [email protected](59146) /postgres/
[unknown] |6a2fee11.cc5|:1 (0): > FATAL: the database system is shutting
down
2026-06-15 15:20:34.643 [3271] [email protected](59150) /postgres/
[unknown] |6a2fee12.cc7|:1 (0): > FATAL: the database system is shutting
down
2026-06-15 15:20:36.024 [3273] [email protected](59154) /postgres/
[unknown] |6a2fee14.cc9|:1 (0): > FATAL: the database system is shutting
down
2026-06-15 15:20:36.051 [3274] [email protected](59158) /postgres/
[unknown] |6a2fee14.cca|:1 (0): > FATAL: the database system is shutting
down
2026-06-15 15:20:40.009 [3282] [email protected](59162) /postgres/
[unknown] |6a2fee18.cd2|:1 (0): > FATAL: the database system is shutting
down
2026-06-15 15:20:51.059 [3291] [email protected](59166) /postgres/
[unknown] |6a2fee23.cdb|:1 (0): > FATAL: the database system is shutting
down
After rolling back to version 14.22, everything works as intended.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 13:39 BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. PG Bug reporting form <[email protected]>
@ 2026-06-15 17:44 ` Andrey Borodin <[email protected]>
2026-06-16 03:46 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Michael Paquier <[email protected]>
2026-06-16 18:36 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Álvaro Herrera <[email protected]>
0 siblings, 2 replies; 7+ messages in thread
From: Andrey Borodin @ 2026-06-15 17:44 UTC (permalink / raw)
To: [email protected]; [email protected]
> On 15 Jun 2026, at 18:39, PG Bug reporting form <[email protected]> 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.
Best regards, Andrey Borodin.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 13:39 BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. PG Bug reporting form <[email protected]>
2026-06-15 17:44 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
@ 2026-06-16 03:46 ` Michael Paquier <[email protected]>
1 sibling, 0 replies; 7+ messages in thread
From: Michael Paquier @ 2026-06-16 03:46 UTC (permalink / raw)
To: Andrey Borodin <[email protected]>; +Cc: [email protected]; [email protected]
On Mon, Jun 15, 2026 at 10:44:31PM +0500, Andrey Borodin wrote:
> 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.
Looking at the set of changes in the range REL_14_22..REL_14_23, we
don't have many things related to recovery, so if you can provide more
details we will likely be able to point to a cause. Without more
information there is nothing that we can unfortunately do.
One thing that I suspect is some custom extension code that may live
outside of core. I have not heard about cases similar to the one
here, and it's been more than 4 weeks since this 14.23 has been
released.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc)
download
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 13:39 BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. PG Bug reporting form <[email protected]>
2026-06-15 17:44 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
@ 2026-06-16 18:36 ` Álvaro Herrera <[email protected]>
2026-06-16 18:43 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
1 sibling, 1 reply; 7+ messages in thread
From: Álvaro Herrera @ 2026-06-16 18:36 UTC (permalink / raw)
To: Andrey Borodin <[email protected]>; +Cc: [email protected]; [email protected]
On 2026-Jun-15, Andrey Borodin wrote:
> > On 15 Jun 2026, at 18:39, PG Bug reporting form <[email protected]> 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)
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 13:39 BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. PG Bug reporting form <[email protected]>
2026-06-15 17:44 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
2026-06-16 18:36 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Álvaro Herrera <[email protected]>
@ 2026-06-16 18:43 ` Andrey Borodin <[email protected]>
2026-06-17 16:49 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Сергей Дм. Апойченко <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Andrey Borodin @ 2026-06-16 18:43 UTC (permalink / raw)
To: Álvaro Herrera <[email protected]>; +Cc: [email protected]; PostgreSQL mailing lists <[email protected]>
> On 16 Jun 2026, at 23:36, Álvaro Herrera <[email protected]> wrote:
>
> On 2026-Jun-15, Andrey Borodin wrote:
>
>>> On 15 Jun 2026, at 18:39, PG Bug reporting form <[email protected]> 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.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 13:39 BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. PG Bug reporting form <[email protected]>
2026-06-15 17:44 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
2026-06-16 18:36 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Álvaro Herrera <[email protected]>
2026-06-16 18:43 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
@ 2026-06-17 16:49 ` Сергей Дм. Апойченко <[email protected]>
2026-06-17 23:27 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Michael Paquier <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: Сергей Дм. Апойченко @ 2026-06-17 16:49 UTC (permalink / raw)
To: Andrey Borodin <[email protected]>; Álvaro Herrera <[email protected]>; +Cc: PostgreSQL mailing lists <[email protected]>
<div><div><div>Good day to everyone!</div><div> </div><div>Last night I performed a switchover in the cluster.</div><div> </div><div>Today I tried to catch an error when updating 14.19 ==> 14.23 on the old primary, but everything worked as expected.</div><div>The database started and connected to the replication slot on the new primary.</div><div> </div><div>##STANDBY_LOG</div><div><div>2026-06-17 14:16:08.367 [18915] @ // |6a305dc8.49e3|:8 (0): > LOG: received fast shutdown request</div><div>2026-06-17 14:16:08.368 [18915] @ // |6a305dc8.49e3|:9 (0): > LOG: aborting any active transactions</div><div>...</div><div>2026-06-17 14:16:18.318 [19845] @ // |6a305dc9.4d85|:462 (0): > LOG: restartpoint complete: wrote 1352773 buffers (32.3%); 0 WAL file(s) added, 14 removed, 14 recycled; write=661.408 s, sync=1.035 s, total=663.019 s; sync files=1196, longest=0.039 s, average=0.001 s; distance=3668114 kB, estimate=5645168 kB</div><div>2026-06-17 14:16:18.318 [19845] @ // |6a305dc9.4d85|:463 (0): > LOG: recovery restart point at C326/AA442CA8</div><div>2026-06-17 14:16:18.318 [19845] @ // |6a305dc9.4d85|:464 (0): > DETAIL: Last completed transaction was at log time 2026-06-17 14:16:08.367471+03.</div><div>2026-06-17 14:16:18.320 [19845] @ // |6a305dc9.4d85|:465 (0): > LOG: shutting down</div><div>2026-06-17 14:16:18.386 [18915] @ // |6a305dc8.49e3|:10 (0): > LOG: database system is shut down</div><div>...</div><div>2026-06-17 14:33:58.250 [24198] @ // |6a3285e1.5e86|:4 (0):1/0 > LOG: consistent recovery state reached at C329/102596D0</div><div>2026-06-17 14:33:58.250 [24198] @ // |6a3285e1.5e86|:5 (0):1/0 > LOG: invalid record length at C329/102596D0: wanted 24, got 0</div><div>2026-06-17 14:33:58.251 [24195] @ // |6a3285e0.5e83|:7 (0): > LOG: database system is ready to accept read-only connections</div><div>2026-06-17 14:33:58.260 [24437] @ // |6a328626.5f75|:1 (0): > LOG: started streaming WAL from primary at C329/10000000 on timeline 7</div></div></div></div><div> </div><div><div>It doesn't seem to be a code error, but rather a configuration issue on the server itself.</div></div><div>Given that I cannot provide any additional information and was unable to reproduce the error, I would like to close the ticket.</div><div><div>Thank you for your response.</div></div><div> </div><div><div> </div><div>С уважением,</div><div>Сергей Дм. Апойченко.</div><div> </div></div><div> </div><div> </div><div> </div><div>----------------</div><div>Кому: Álvaro Herrera (<a href="mailto:[email protected]" rel="noopener noreferrer">[email protected]</a>);</div><div>Копия: PostgreSQL mailing lists (<a href="mailto:[email protected]" rel="noopener noreferrer">[email protected]</a>);</div><div>Тема: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.;</div><div>16.06.2026, 23:43, "Andrey Borodin" <<a href="mailto:[email protected]" rel="noopener noreferrer">[email protected]</a>>:</div><blockquote><p><br /> </p><blockquote> On 16 Jun 2026, at 23:36, Álvaro Herrera <<a href="mailto:[email protected]" rel="noopener noreferrer">[email protected]</a>> wrote:<br /> <br /> On 2026-Jun-15, Andrey Borodin wrote:<br /> <blockquote><blockquote> On 15 Jun 2026, at 18:39, PG Bug reporting form <<a href="mailto:[email protected]" rel="noopener noreferrer">[email protected]</a>> wrote:<br /> <br /> After rolling back to version 14.22, everything works as intended.</blockquote> <br /> Hi! Thanks for the report. Can you please give a bit more logs? This excerpt is<br /> missing errors from the startup process. And message from this process could shed<br /> a light on a root cause.</blockquote> <br /> I suspect e35e466f61b [1] might be related. That's a bug that was<br /> fixed in 2bb60eb4fea [2], just after 14.23.<br /> <br /> [1] <a href="https://postgr.es/c/e35e466f61b"; rel="noopener noreferrer">https://postgr.es/c/e35e466f61b</a><br /> [2] <a href="https://postgr.es/c/2bb60eb4fea"; rel="noopener noreferrer">https://postgr.es/c/2bb60eb4fea</a><br /> <br /> If not, some data from pg_waldump around the problem area might be useful.</blockquote><p><br />Yeah, that was my concern. But that bug manifests as startup process failure.<br />I've contacted Sergey offlist, he observed hanging<br /><br />postgres: data: startup recovering 000000060000C29100000016<br /><br />so it's hard to tell what's going on without backtrace...<br /><br /><br />Best regards, Andrey Borodin.</p></blockquote>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 13:39 BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. PG Bug reporting form <[email protected]>
2026-06-15 17:44 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
2026-06-16 18:36 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Álvaro Herrera <[email protected]>
2026-06-16 18:43 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Andrey Borodin <[email protected]>
2026-06-17 16:49 ` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. Сергей Дм. Апойченко <[email protected]>
@ 2026-06-17 23:27 ` Michael Paquier <[email protected]>
0 siblings, 0 replies; 7+ messages in thread
From: Michael Paquier @ 2026-06-17 23:27 UTC (permalink / raw)
To: Сергей Дм. Апойченко <[email protected]>; +Cc: Andrey Borodin <[email protected]>; Álvaro Herrera <[email protected]>; PostgreSQL mailing lists <[email protected]>
On Wed, Jun 17, 2026 at 09:49:22PM +0500, Сергей Дм. Апойченко wrote:
> It doesn't seem to be a code error, but rather a configuration issue
> on the server itself. Given that I cannot provide any additional
> information and was unable to reproduce the error, I would like to
> close the ticket. Thank you for your response.
Okay, thanks for the update. The handling of multixacts during
recovery has already been tweaked a bit. I think that we are in a
good spot in terms of lock handling in the stable branches, but if you
still see something strange, please feel free to update this thread
with more information for investigation.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc)
download
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2026-06-17 23:27 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-06-15 13:39 BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. PG Bug reporting form <[email protected]>
2026-06-15 17:44 ` Andrey Borodin <[email protected]>
2026-06-16 03:46 ` Michael Paquier <[email protected]>
2026-06-16 18:36 ` Álvaro Herrera <[email protected]>
2026-06-16 18:43 ` Andrey Borodin <[email protected]>
2026-06-17 16:49 ` Сергей Дм. Апойченко <[email protected]>
2026-06-17 23:27 ` Michael Paquier <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox