BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
Date
Msg-id 19521-4cdc3a548f506cf8@postgresql.org
Whole thread
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      19521
Logged by:          Sergey Apoychenko
Email address:      sdaekb@yandex.ru
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] postgres@127.0.0.1(58784) /postgres/
[unknown] |6a2fed57.a16|:2 (0): > DETAIL:  Consistent recovery state has not
been yet reached.
2026-06-15 15:17:28.543 [2584] postgres@127.0.0.1(58788) /postgres/
[unknown] |6a2fed58.a18|:1 (0): > FATAL:  the database system is not yet
accepting connections
2026-06-15 15:17:28.543 [2584] postgres@127.0.0.1(58788) /postgres/
[unknown] |6a2fed58.a18|:2 (0): > DETAIL:  Consistent recovery state has not
been yet reached.
2026-06-15 15:17:29.736 [2586] postgres@127.0.0.1(58792) /postgres/
[unknown] |6a2fed59.a1a|:1 (0): > FATAL:  the database system is not yet
accepting connections
2026-06-15 15:17:29.736 [2586] postgres@127.0.0.1(58792) /postgres/
[unknown] |6a2fed59.a1a|:2 (0): > DETAIL:  Consistent recovery state has not
been yet reached.
2026-06-15 15:17:32.329 [2589] postgres@127.0.0.1(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] postgres@127.0.0.1(59146) /postgres/
[unknown] |6a2fee11.cc5|:1 (0): > FATAL:  the database system is shutting
down
2026-06-15 15:20:34.643 [3271] postgres@127.0.0.1(59150) /postgres/
[unknown] |6a2fee12.cc7|:1 (0): > FATAL:  the database system is shutting
down
2026-06-15 15:20:36.024 [3273] postgres@127.0.0.1(59154) /postgres/
[unknown] |6a2fee14.cc9|:1 (0): > FATAL:  the database system is shutting
down
2026-06-15 15:20:36.051 [3274] postgres@127.0.0.1(59158) /postgres/
[unknown] |6a2fee14.cca|:1 (0): > FATAL:  the database system is shutting
down
2026-06-15 15:20:40.009 [3282] postgres@127.0.0.1(59162) /postgres/
[unknown] |6a2fee18.cd2|:1 (0): > FATAL:  the database system is shutting
down
2026-06-15 15:20:51.059 [3291] postgres@127.0.0.1(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.





pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
Next
From: Melanie Plageman
Date:
Subject: Re: Autoprewarm workers terminated due to a segmentation fault