From e64aa1a39d4b8a9502be8ed8dfd67efd6f6acf28 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Fri, 17 Oct 2025 14:03:42 +0900 Subject: [PATCH] doc: Clarify when backend_xmin in pg_stat_replication can be NULL. Improve the documentation of pg_stat_replication to explain when the backend_xmin column becomes NULL. This happens when a replication slot is used (the xmin is then shown in pg_replication_slots) or when hot_standby_feedback is disabled. Author: Renzo Dani Reviewed-by: Fujii Masao Discussion: https://postgr.es/m/CA+XOKQAMXzskpdUmj2sg03_5fmiXc2Gs0r3TX1_rmcFcqh+=xQ@mail.gmail.com --- doc/src/sgml/monitoring.sgml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index dc4fc29466d..d5f0fb7ba7c 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1287,6 +1287,10 @@ description | Waiting for a newly initialized WAL file to reach durable storage This standby's xmin horizon reported by . + This field will be null if a replication slot is used (in this case, + the standby's xmin is shown in + pg_replication_slots) + or if hot_standby_feedback is disabled.