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 1wfacm-005Wjp-2P for pgsql-admin@arkaria.postgresql.org; Fri, 03 Jul 2026 09:55:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wfacl-006gLv-17 for pgsql-admin@arkaria.postgresql.org; Fri, 03 Jul 2026 09:55:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wfack-006gLm-2N for pgsql-admin@lists.postgresql.org; Fri, 03 Jul 2026 09:55:54 +0000 Received: from mail-pg1-x529.google.com ([2607:f8b0:4864:20::529]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wfaci-00000001IN9-0wCv for pgsql-admin@postgresql.org; Fri, 03 Jul 2026 09:55:53 +0000 Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-c89636920a3so185724a12.1 for ; Fri, 03 Jul 2026 02:55:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1783072551; cv=none; d=google.com; s=arc-20260327; b=ZEg+6ylWzBKbozYvDGeiK7ECT42drYDfoNBD28rqzk7pHO50zQmtkOXePVJKB7De04 7pTuXyGnr4v2iYyPpEmZe1D04TDam5LrBXaywx/fUCq94JR6lPkcZ84wnlxdZf0JpTDu 5fFVKJkAFRX20OpD8oOD+SzevlKrrD+pXkdO7G6FDNp4Dw1KGnBmklhIqmbUsJl+eElp HDfbE3MTO3ZUncVGP7pql/8x+Ue3WjUHDnDFcbYs5VP6vRadKn+qGH40evNTkQacLeoJ X0oQ0X8aBHKGLVeF+t/tiDOdO9UvSTdu8KXBPg6Q32tdWwoitgA1Kk78r60+z1BaxRN8 9jLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=to:subject:message-id:date:from:mime-version:dkim-signature; bh=WmUZjENivZ65+3x9oGYyL7tAU5HL+8z5AxLHYeLPeSM=; fh=tUEujQkkzQH7hpl2/0TP1TJZlxgI78/I2COq56NPtnA=; b=QlAbJa3zXnAVTePYwPHBdbcqKKlOcoDceIWruMGAZgivIAdX7LnIuQ5AMiYSOOgxS7 PKlJc9TdsMvq8TxgkcK57a4ESBldkxZtefXRWq+igTlSjRLP56ah8J90JrqreAodbjVf SG21HLA6CC13hAh4x+cjXT+H0e7Ruh+lC8czlOlsunjS47XIxRdo6Pdg2NgkOmqUeHXr qPLY0UDrL3fLtmwBJngZjgYBKXHrpKPZa7ptmoZhcM3y7XJUjn2/ci2kT/lhKLcM/Gnw ZXRF+YcaKL/FisezKghYDV/BBLN46k7QHWhTDSFK0OSndDoH4Se3i6CPWHSt7nk0vWc6 Yumw==; darn=postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1783072551; x=1783677351; darn=postgresql.org; h=content-type:to:subject:message-id:date:from:mime-version:from:to :cc:subject:date:message-id:reply-to:content-type; bh=WmUZjENivZ65+3x9oGYyL7tAU5HL+8z5AxLHYeLPeSM=; b=a+I/XQs/nuRdrqJl4iipNMaROjtu5QRU4cliht1h64iDLiJd3mwWSLrKDGp3IPBIcS +mSwSHQ6oIMrg/MyzSrM2efoScblR5s6tw8fIlYsRCyjvq1jd7qAsN07Kj9uN3HpBpD5 KsebMmAhEkczMqfSgeGzPt+AFLhOs0ZSXwNahsWwN8gp39ubpeTfeZJHQlWHzPT/TZqj eJtXb7zdTRxjBEOyV7uN1UQcFRWU0a0DJN9SfbuoXH+dIEQoqNu+bsqb9COn7VFbfMl/ rCFDHsI2N4bXCscm56f1RRr/MhZ9bZXIeeoTeU3pBMXjWDz4Ciwhg2b9bEqGiKFzXkqX OAeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1783072551; x=1783677351; h=content-type:to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=WmUZjENivZ65+3x9oGYyL7tAU5HL+8z5AxLHYeLPeSM=; b=TZoUpPjTvR0NqEcwqK4jZDMzrFZ41rfsIoiiy2Sg/u2aGUPUDqqbC/O1GJyyjNZbcK s+0QndrQIuFt8KmM+X7yV12Af73PPOAzBfeW0lSaIirvqMwD0mdE/VRSnYPthqmWl/tC QkymlcqffrD8K8hSsDFNGWLTWa50G8dElARwf4j8xzjmnxV8jD7KZMOaLI1YlsmYCRtO Qtt7xr0QYCTC3xII/ewosI9b3VTYmojCO670klBe/GLnY7llqAqaWK7dRK9kUo0cffQ1 56fkvzWB5+mwomhZnLT/caeC8dyB5kL5/8Wqxfn8PXa/dPUn7nUOnet2KJH/e/jMhR/Q 5cDA== X-Gm-Message-State: AOJu0YxczovT6/R2PxWj0/WEF1lzoqpf13WS1xuLHJMEw55CT5FZjrNf 316olgtkVLsUisLzgicLTZs1kWQfZhbjTrNd6eAtvoGOJOdu8keC6k59TvulJ09P7vgJ8dCGIxV 4gnO1yVDNRrDLm1ugDWFs1UBZUN/SpF4YtgVn X-Gm-Gg: AfdE7cl7S+MnAbYCtGwj8rTmLQ5vnHE615kpqPttREI8Eyy4VwFGzE+wLdrbRubn9Hh HTmbyIb86ZnzL5xsA0jN4xarVtwo8Ujvhs7sbr9eWnL3YA2ANDTtTgyNFiOcTOqMRB17HQayFNf KXEMj/y16Et3tTTeUB6ahQT+GjEBd86QAkXjGtOvQLTNZ3n7TgRk9XLaozyVnb43T5IG4z0HYEM nMN81GQfada7aA5HxGRjefbYi+VJsTas10azBv+ZCRbljoCvXFFHm6mCVE5VA2j3Kh0ooWf X-Received: by 2002:a05:6a20:5493:b0:39b:d5f1:4ff with SMTP id adf61e73a8af0-3bff40a53d7mr11712494637.20.1783072550569; Fri, 03 Jul 2026 02:55:50 -0700 (PDT) MIME-Version: 1.0 From: K P Manoj Date: Fri, 3 Jul 2026 15:25:35 +0530 X-Gm-Features: AVVi8CdXTs8scpAXNppqCISvW00w6znLBKs1VxO-yvSvXhVdCxnwPkPQBwQQjqk Message-ID: Subject: PG version 16.14 upgrade went recovery state To: "pgsql-admin@postgresql.org" Content-Type: multipart/alternative; boundary="000000000000fc4c3f0655b1ed77" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fc4c3f0655b1ed77 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable K P Manoj 12:24=E2=80=AFPM (3 hours ago) to pgsql-hackers, pgsql-bugs Hi Team, I am encountering an issue when upgrading our PostgreSQL database from minor version 16.10 to 16.14. During the upgrade, the database enters an indefinite recovery mode across the master, standby, and multiple cascading replicas. Due to legacy requirements, we are utilizing streaming replication for this setup. Interestingly, when performing the same migration to version 16.13, the process completes successfully without any issues. Could you please confirm if there are any known bugs regarding this behavior in version 16.14? For reference, please find the details of our test steps and logs below. 1. Upgrade Attempt to Version 16.14 (Database Stays in Recovery Mode) Version Check: root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# /usr/local/pgsql/bin/psql --version psql (PostgreSQL) 16.14 Process Status: root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# ps -ef|grep rec postgres 48 43 1 15:28 ? 00:00:01 postgres: startup recovering 0000000100002499000000E4 root 166 58 0 15:30 pts/0 00:00:00 grep --color=3Dauto rec WAL Directory Details: root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# ls -l 0000000100002499000000E4 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:25 0000000100002499000000E4 root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# ls -lt|more total 55001312 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:54 000000010000249A00000059 drwxrws--- 2 postgres postgres 225280 Jul 2 14:54 archive_status -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:54 000000010000249A00000058 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:54 000000010000249A00000057 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:54 000000010000249A00000056 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:54 000000010000249A00000055 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A00000054 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A00000053 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A00000052 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A00000051 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A00000050 -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A0000004F -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A0000004E -rw-rw---- 1 postgres postgres 16777216 Jul 2 14:53 000000010000249A0000004D PostgreSQL Logs: 2026-07-02 15:28:38.709 UTC [43]: [3-1] user=3D,db=3D >LOG: starting PostgreSQL 16.14 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, 64-bit 2026-07-02 15:28:38.709 UTC [43]: [4-1] user=3D,db=3D >LOG: listening on = IPv4 address "0.0.0.0", port 5432 2026-07-02 15:28:38.709 UTC [43]: [5-1] user=3D,db=3D >LOG: listening on = IPv6 address "::", port 5432 2026-07-02 15:28:38.722 UTC [43]: [6-1] user=3D,db=3D >LOG: listening on = Unix socket "/tmp/.s.PGSQL.5432" 2026-07-02 15:28:38.753 UTC [48]: [1-1] user=3D,db=3D >LOG: database syst= em was interrupted while in recovery at log time 2026-07-02 14:22:09 UTC 2026-07-02 15:28:38.753 UTC [48]: [2-1] user=3D,db=3D >HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target. 2026-07-02 15:28:38.979 UTC [48]: [3-1] user=3D,db=3D >LOG: entering stan= dby mode 2026-07-02 15:28:38.993 UTC [48]: [4-1] user=3D,db=3D >LOG: redo starts a= t 2499/CFF32450 2026-07-02 15:28:47.282 UTC [49]: [1-1] user=3D127.0.0.1,db=3Dpostgres >FA= TAL: the database system is not yet accepting connections 2026-07-02 15:28:47.282 UTC [49]: [2-1] user=3D127.0.0.1,db=3Dpostgres >DETAIL: Consistent recovery state has not been yet reached. 2026-07-02 15:28:57.291 UTC [57]: [1-1] user=3D127.0.0.1,db=3Dpostgres >FA= TAL: the database system is not yet accepting connections 2026-07-02 15:28:57.291 UTC [57]: [2-1] user=3D127.0.0.1,db=3Dpostgres >DETAIL: Consistent recovery state has not been yet reached. 2. Successful Migration to Version 16.13 (Streaming Replication Working) Version Check: root@pgreplica-master-0:/# psql --version psql (PostgreSQL) 16.13 (Debian 16.13-1.pgdg12+1) Process Status (Walreceiver Streaming Active): root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# ps -ef|grep rec postgres 48 43 32 15:40 ? 00:00:20 postgres: startup recovering 000000010000249B0000002E postgres 50 43 7 15:40 ? 00:00:03 postgres: walreceiver streaming 249B/2E660000 root 105 80 0 15:41 pts/0 00:00:00 grep rec WAL File Check: root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# ls -lth 000000010000249B0000002E -rw------- 1 postgres postgres 16M Jul 2 15:41 000000010000249B0000002E Database Connection Verification: root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# psql -U postgres -c " select version () " version ---------------------------------------------------------------------------= --------------------------------------------------- PostgreSQL 16.13 (Debian 16.13-1.pgdg12+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit (1 row) Please let me know if any further details or logs are required to investigate this issue. Best regards, Manoj K P --000000000000fc4c3f0655b1ed77 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=

K P Manoj=C2=A0<kpmanojpg@gmail.com>

12:24=E2=80=AFPM (3 hours ago)
=
=
to=C2=A0pgsql-ha= ckers,=C2=A0pgsql-bugs
3D""
Hi Team,

I am encountering an issue when upgrading ou= r PostgreSQL database from minor version 16.10 to 16.14.

During the = upgrade, the database enters an indefinite recovery mode across the master,= standby, and multiple cascading replicas. Due to legacy requirements, we a= re utilizing streaming replication for this setup. Interestingly, when perf= orming the same migration to version 16.13, the process completes successfu= lly without any issues.

Could you please confirm if there are any kn= own bugs regarding this behavior in version 16.14?

For reference, pl= ease find the details of our test steps and logs below.

1. Upgrade A= ttempt to Version 16.14 (Database Stays in Recovery Mode)

Version Ch= eck:

root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# /usr/l= ocal/pgsql/bin/psql --version
psql (PostgreSQL) 16.14

Process Sta= tus:

root@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# ps -ef= |grep rec
postgres =C2=A0 =C2=A0 =C2=A048 =C2=A0 =C2=A0 =C2=A043 =C2=A01= 15:28 ? =C2=A0 =C2=A0 =C2=A0 =C2=A000:00:01 postgres: startup recovering 0= 000000100002499000000E4
root =C2=A0 =C2=A0 =C2=A0 =C2=A0 166 =C2=A0 =C2= =A0 =C2=A058 =C2=A00 15:30 pts/0 =C2=A0 =C2=A000:00:00 grep --color=3Dauto = rec

WAL Directory Details:

root@pgreplica-master-0:/var/lib/p= ostgresql/data/pg_wal# ls -l 0000000100002499000000E4
-rw-rw---- 1 postg= res postgres 16777216 Jul =C2=A02 14:25 0000000100002499000000E4

roo= t@pgreplica-master-0:/var/lib/postgresql/data/pg_wal# ls -lt|more
total = 55001312
-rw-rw---- 1 postgres postgres 16777216 Jul =C2=A02 14:54 00000= 0010000249A00000059
drwxrws--- 2 postgres postgres =C2=A0 225280 Jul =C2= =A02 14:54 archive_status
-rw-rw---- 1 postgres postgres 16777216 Jul = =C2=A02 14:54 000000010000249A00000058
-rw-rw---- 1 postgres postgres 16= 777216 Jul =C2=A02 14:54 000000010000249A00000057
-rw-rw---- 1 postgres = postgres 16777216 Jul =C2=A02 14:54 000000010000249A00000056
-rw-rw---- = 1 postgres postgres 16777216 Jul =C2=A02 14:54 000000010000249A00000055
= -rw-rw---- 1 postgres postgres 16777216 Jul =C2=A02 14:53 000000010000249A0= 0000054
-rw-rw---- 1 postgres postgres 16777216 Jul =C2=A02 14:53 000000= 010000249A00000053
-rw-rw---- 1 postgres postgres 16777216 Jul =C2=A02 1= 4:53 000000010000249A00000052
-rw-rw---- 1 postgres postgres 16777216 Ju= l =C2=A02 14:53 000000010000249A00000051
-rw-rw---- 1 postgres postgres = 16777216 Jul =C2=A02 14:53 000000010000249A00000050
-rw-rw---- 1 postgre= s postgres 16777216 Jul =C2=A02 14:53 000000010000249A0000004F
-rw-rw---= - 1 postgres postgres 16777216 Jul =C2=A02 14:53 000000010000249A0000004E-rw-rw---- 1 postgres postgres 16777216 Jul =C2=A02 14:53 000000010000249= A0000004D

PostgreSQL Logs:

2026-07-02 15:28:38.709 UTC [43]: = [3-1] user=3D,db=3D =C2=A0>LOG: =C2=A0starting PostgreSQL 16.14 on x86_6= 4-pc-linux-gnu, compiled by gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, 64= -bit
2026-07-02 15:28:38.709 UTC [43]: [4-1] user=3D,db=3D =C2=A0>LOG= : =C2=A0listening on IPv4 address "0.0.0.0", port 5432
2026-07= -02 15:28:38.709 UTC [43]: [5-1] user=3D,db=3D =C2=A0>LOG: =C2=A0listeni= ng on IPv6 address "::", port 5432
2026-07-02 15:28:38.722 UTC= [43]: [6-1] user=3D,db=3D =C2=A0>LOG: =C2=A0listening on Unix socket &q= uot;/tmp/.s.PGSQL.5432"
2026-07-02 15:28:38.753 UTC [48]: [1-1] use= r=3D,db=3D =C2=A0>LOG: =C2=A0database system was interrupted while in re= covery at log time 2026-07-02 14:22:09 UTC
2026-07-02 15:28:38.753 UTC [= 48]: [2-1] user=3D,db=3D =C2=A0>HINT: =C2=A0If this has occurred more th= an once some data might be corrupted and you might need to choose an earlie= r recovery target.
2026-07-02 15:28:38.979 UTC [48]: [3-1] user=3D,db=3D= =C2=A0>LOG: =C2=A0entering standby mode
2026-07-02 15:28:38.993 UTC = [48]: [4-1] user=3D,db=3D =C2=A0>LOG: =C2=A0redo starts at 2499/CFF32450=
2026-07-02 15:28:47.282 UTC [49]: [1-1] user=3D127.0.0.1,db=3Dpostgres = =C2=A0>FATAL: =C2=A0the database system is not yet accepting connections=
2026-07-02 15:28:47.282 UTC [49]: [2-1] user=3D127.0.0.1,db=3Dpostgres = =C2=A0>DETAIL: =C2=A0Consistent recovery state has not been yet reached.=
2026-07-02 15:28:57.291 UTC [57]: [1-1] user=3D127.0.0.1,db=3Dpostgres = =C2=A0>FATAL: =C2=A0the database system is not yet accepting connections=
2026-07-02 15:28:57.291 UTC [57]: [2-1] user=3D127.0.0.1,db=3Dpostgres = =C2=A0>DETAIL: =C2=A0Consistent recovery state has not been yet reached.=

2. Successful Migration to Version 16.13 (Streaming Replication Wor= king)

Version Check:

root@pgreplica-master-0:/# psql --versio= n
psql (PostgreSQL) 16.13 (Debian 16.13-1.pgdg12+1)

Process Statu= s (Walreceiver Streaming Active):

root@pgreplica-master-0:/var/lib/p= ostgresql/data/pg_wal# ps -ef|grep rec
postgres =C2=A0 =C2=A0 =C2=A048 = =C2=A0 =C2=A0 =C2=A043 32 15:40 ? =C2=A0 =C2=A0 =C2=A0 =C2=A000:00:20 postg= res: startup recovering 000000010000249B0000002E
postgres =C2=A0 =C2=A0 = =C2=A050 =C2=A0 =C2=A0 =C2=A043 =C2=A07 15:40 ? =C2=A0 =C2=A0 =C2=A0 =C2=A0= 00:00:03 postgres: walreceiver streaming 249B/2E660000
root =C2=A0 =C2= =A0 =C2=A0 =C2=A0 105 =C2=A0 =C2=A0 =C2=A080 =C2=A00 15:41 pts/0 =C2=A0 =C2= =A000:00:00 grep rec

WAL File Check:

root@pgreplica-master-0:= /var/lib/postgresql/data/pg_wal# ls -lth 000000010000249B0000002E
-rw---= ---- 1 postgres postgres 16M Jul =C2=A02 15:41 000000010000249B0000002E
=
Database Connection Verification:

root@pgreplica-master-0:/var/l= ib/postgresql/data/pg_wal# psql -U postgres -c " select version () &qu= ot;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0versio= n =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
--= ---------------------------------------------------------------------------= -------------------------------------------------
=C2=A0PostgreSQL 16.13= (Debian 16.13-1.pgdg12+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian = 12.2.0-14+deb12u1) 12.2.0, 64-bit
(1 row)

Please let me know if a= ny further details or logs are required to investigate this issue.

B= est regards,

Manoj K P

--000000000000fc4c3f0655b1ed77--