database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-19 15:49:24 +03:00
Code Activity

doc: Clarify when backend_xmin in pg_stat_replication can be NULL.

Browse Source 
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 <arons7@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
Discussion: https://postgr.es/m/CA+XOKQAMXzskpdUmj2sg03_5fmiXc2Gs0r3TX1_rmcFcqh+=xQ@mail.gmail.com
This commit is contained in:
Fujii Masao
2025-10-17 14:03:42 +09:00
parent d1b80a31ed
commit e64aa1a39d
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/monitoring.sgml
View File

@@ -1287,6 +1287,10 @@ 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 this case,
the standby's <literal>xmin</literal> is shown in
<link linkend="view-pg-replication-slots">pg_replication_slots</link>)
or if <varname>hot_standby_feedback</varname> is disabled.
</para></entry>
</row>