Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wZATL-000pBu-0X for pgsql-bugs@arkaria.postgresql.org; Mon, 15 Jun 2026 16:47:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wZATJ-00CgmP-21 for pgsql-bugs@arkaria.postgresql.org; Mon, 15 Jun 2026 16:47:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wZ7Xt-00C8g8-0e for pgsql-bugs@lists.postgresql.org; Mon, 15 Jun 2026 13:40:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wZ7Xq-00000000Wdu-2TPr for pgsql-bugs@lists.postgresql.org; Mon, 15 Jun 2026 13:40:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=GPQc1UIB6w92sbnde+Z9Dw4UQaV9RsUY6bXAIrJafww=; b=mbWsizYhodZ52PTM+aZeeBG66B gKpuKWhyrVWMFg/ZqGYSQA3fO9yucGJu3SA0dm9PnHdVFDg/0pWzM35AuvVLeT2QurbtLLJBsUctm oQNOjhXuuNHUvvqPpENzyazG1NOtC0ObJBx5b7S073fdQIaduMnevRQjNo+ddJrBeimkZmZBu2EKD WI6f6Uiz+Yhhb+MdGVCvRXS30qm5K9ytOvKr+7lvzgk78PDMrTkO4L5adkhHFeoZYLWYOefjCve9r 0mo25NgtWuD++mw2RE3ve2q/KErRfVr0VC+vs0UeBSBreAPq6hIFaoD2USkoD5cJ7WdVYhg+IpGbm NkP9r0eA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wZ7Xo-001WJG-0G for pgsql-bugs@lists.postgresql.org; Mon, 15 Jun 2026 13:40:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wZ7Xm-0031cl-2U for pgsql-bugs@lists.postgresql.org; Mon, 15 Jun 2026 13:40:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: sdaekb@yandex.ru Reply-To: sdaekb@yandex.ru, pgsql-bugs@lists.postgresql.org Date: Mon, 15 Jun 2026 13:39:54 +0000 Message-ID: <19521-4cdc3a548f506cf8@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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: =20 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.