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.94.2) (envelope-from ) id 1vGK7U-00CVNx-Uk for pgsql-admin@arkaria.postgresql.org; Tue, 04 Nov 2025 16:42:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vGK7T-00F2v1-Rq for pgsql-admin@arkaria.postgresql.org; Tue, 04 Nov 2025 16:42:54 +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.94.2) (envelope-from ) id 1vGK7T-00F2td-Fm for pgsql-admin@lists.postgresql.org; Tue, 04 Nov 2025 16:42:54 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vGK7Q-005xh6-1W for pgsql-admin@lists.postgresql.org; Tue, 04 Nov 2025 16:42:54 +0000 Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-b403bb7843eso255490166b.3 for ; Tue, 04 Nov 2025 08:42:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762274571; x=1762879371; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=DTkFOLhGU8JhITF3q9HbGAzldrRe6FcTvIoS2NAdQ6Y=; b=QMTMwULzo5UbQG8r21m6+aZJlVntFEIJCVeQqynPxKm3rpN2/T4AHKlXB+GAjkgZQW 597tPSiE2bFDiR6hDjWVUOlf4cspnVOsxZ2V/JdpwMJ8oY+iZEuihquqbqYiwhU9ggu+ OiwdAgSLIgWTtYAvCpSJUuP8eo+9BK1XFiyYY5mrmGIT5GuF+zYisaudJvnlVEXLGIb8 UfU+eunl07CJqTcBjhUnkTon2AQTiZGNCNc+klSud93JgsajBduSIM/H8gUadjTQNR9I AG4WvhTBVP2QdwjzLGi+YPEgB670z4OWmkTqHUqluUyunYrpmiJhs2OKeF3oSxZu7wkb SPZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762274571; x=1762879371; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=DTkFOLhGU8JhITF3q9HbGAzldrRe6FcTvIoS2NAdQ6Y=; b=Y8ZAYxPkyWiR0KQPhmLVLbPScYg4caJW4s6jToL587k4avRcemwraRzMRs2keMfOzx +ZNV0NYGiHa2u8zFsgkwpUpUFE/RekxxDiNyQb6z4Y/JWSi1Lz/CjwcMEsUAUndsU1KH M3prmocmPYQFJQJG7mywkSbPhrol7E+9067+j8clMuSSKJSvXgyNhWs3iitd8zz0s5pG guwsFUcDe/Vl6YAsgptbYyxfr4ua1tvy+ZmgOn7d7OtRxASMzMbByHRVcD5d41bsbNZX xSzQqIB9QX+8eBN+8xoX1CTN+bZ+5prRjDqQkCa9DGMz7NTwn0Hz1GSoFNU2+Qmnbl96 tp+g== X-Gm-Message-State: AOJu0Yyf75fhzVZ79sioYoL2hsRQ47qNOhSeQCuMhNQAEjZbAtRxxM8H uS47hf1irgvpD1Oifv21fQTxzqp5H1hbPTpiZMV/jzy+6eci6FLs5ODnN3CiAubXXDQWAI8YM7H 7ktRyrDKI/dlVVJFTdXK6J4J5v9R2dCRwPQ== X-Gm-Gg: ASbGncuHGo5q/vLEHqGArn9x6icEje0Q6R20z7BE/y6ppXQXvpHTsSmcc/K9sRu5sc7 Ls/X6Z5VBt1KztcCBbVXt2gsJW4cgaC5AaS9z2U+DZKTN/4zfCeN8gqUvZC3Rnmp95NpL8NQd/C YOHssuXRK4RUhFglWpEIjgcKs43oUh1dbHlKQ6WGJ1xunNm7k5DBkDpGjsbfSeLRZMzB77VN09i vex62KREmnQtDdi7TVQ4rMI3UjacTSXzJjbuL/uVpRfRstr56ZSOD7KIgrnBHmhUKuLT3byFtAy GSvGvXGZBTLP3+U= X-Google-Smtp-Source: AGHT+IFSQ/9pvHO8DeTmz0fht8ncxeNvA83WeAwZCTB7UAWdGwZXgTjm1APgI1HtH6nJtXN+TLqqLZ88XQ0BMkL7KjM= X-Received: by 2002:a17:907:3d0e:b0:b3e:f89e:9861 with SMTP id a640c23a62f3a-b70701ac51amr1839147566b.28.1762274570597; Tue, 04 Nov 2025 08:42:50 -0800 (PST) MIME-Version: 1.0 From: Nikhil Shetty Date: Tue, 4 Nov 2025 22:12:38 +0530 X-Gm-Features: AWmQ_bmCw6MIMSysLM5VIMCH8q2XzaQyT9kT6cSvjR5nyjLNnyuLuA6fkWVuaQc Message-ID: Subject: Startup process stuck on WAL replay To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000c6f88a0642c785ad" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c6f88a0642c785ad Content-Type: text/plain; charset="UTF-8" Hi All, The startup process on a replica is stuck on a WAL for a long time LSN - F46/FB4FCF88 We verified this from pg_stat_replication output We did a WAL dump to see the xact for this LSN and it shows as below rmgr: Heap2 len (rec/tot): 56/ 56, tx: 0, lsn: F46/FB4FCF88, prev F46/FB4FCF40, desc: PRUNE latestRemovedXid 884637333 nredirected 0 ndead 1, blkref #0: rel 1663/16402/72663 blk 0 Would such a xact cause WAL replay to get stuck ? Or is it some other issue? Is there any way to check where it is stuck , strace was not helpful Thanks, Nikhil --000000000000c6f88a0642c785ad Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

The startup proce= ss on a replica is stuck on a WAL for a long time=C2=A0
LSN - F46/FB4FCF88

W= e verified=C2=A0this from pg_stat_replication output

We did a WAL dump to see the xact for this LSN= and it shows as below

<= div>

rmgr: Heap2 =C2=A0 =C2=A0 =C2=A0 len (rec/tot): =C2=A0 =C2=A0 56/=C2=A0 = =C2=A0 56, tx:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0, lsn: F46/FB4FCF88, prev= F46/FB4FCF40, desc: PRUNE latestRemovedXid 884637333 nredirected 0 ndead 1= , blkref #0: rel 1663/16402/72663 blk 0

Would such a xact cause WAL replay to get stuck ? Or is it some other= issue? Is there any way to check where it is stuck , strace was not helpfu= l=C2=A0

Thanks,
Nikhil=C2=A0




--000000000000c6f88a0642c785ad--