postgrespro.git / summary / log / commit / refs

commit    e641b2a995abfa0dd7039863e2597feb3abf2b1e
Author:   Amit Kapila <akapila@postgresql.org>
Date:     Tue Jun 02 05:41:25 2020 +0000

    Doc: Update the documentation for spilled transaction statistics.
    
    Reported-by: Sawada Masahiko
    Author: Sawada Masahiko, Amit Kapila
    Reviewed-by: Amit Kapila
    Discussion: https://postgr.es/m/CA+fd4k4vNg7dRO5ECHdtQXXf1=Q4M98pfLW0dU7BKD8h79pkqA@mail.gmail.com


 doc/src/sgml/monitoring.sgml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 321a0f4bb1..89662cc0a3 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -2518,6 +2518,12 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
    mechanism will simply display NULL lag.
   </para>
 
+  <para>
+   Tracking of spilled transactions works only for logical replication.  In
+   physical replication, the tracking mechanism will display 0 for spilled
+   statistics.
+  </para>
+
   <note>
    <para>
     The reported lag times are not predictions of how long it will take for


[parent: b846091fd0a7]