Hi, recently I had some issue understanding what was going on with a replica and the reported xmin. I have than created a patch to better specify the value expected into the pg_stat_replication.backend_xmin field.
Regards, Renzo Dani
From 6ec4b38af5e1f5d90e8de7ef2ac073761a362b5d Mon Sep 17 00:00:00 2001 From: Renzo Dani <[email protected]> Date: Wed, 15 Oct 2025 17:31:45 +0200 Subject: [PATCH] Extend documentation for pg_stat_replication.backend_xmin --- doc/src/sgml/monitoring.sgml | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index dc4fc29466d..c616571e4df 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1287,6 +1287,7 @@ description | Waiting for a newly initialized WAL file to reach durable storage <para> This standby's <literal>xmin</literal> horizon reported by <xref linkend="guc-hot-standby-feedback"/>. + This field will be null if a replication slot is used; in that case, the xmin is available through <link linkend="view-pg-replication-slots">pg_replication_slots</link>. </para></entry> </row> -- 2.43.0
