postgres.git / summary / log / commit / refs

commit    f056f75dafd0025d26efaca026a87f14c079a130
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Wed Mar 26 23:07:54 2025 +0000
First released in: 18.0

    doc: Mention possible ephemeral discrepancies in pg_stat_activity
    
    Ephemeral inconsistencies across multiple attributes of pg_stat_activity
    can exist as the system is designed to be efficient with a low overhead.
    This question is raised by users from time to time based on the data
    read in the view, so let's add a note in the docs about this
    possibility.
    
    Author: Alex Friedman <alexf01@gmail.com>
    Reviewed-by: Sami Imseih <samimseih@gmail.com>
    Discussion: https://postgr.es/m/8a275154-a654-44b0-ab37-197802f04c7b@gmail.com


 doc/src/sgml/monitoring.sgml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 0960f5ba94a..bacc09cb8af 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -1022,7 +1022,9 @@ postgres   27093  0.0  0.0  30096  2752 ?        Ss   11:34   0:00 postgres: ser
     it may or may not be <literal>waiting</literal> on some event.  If the state
     is <literal>active</literal> and <structfield>wait_event</structfield> is non-null, it
     means that a query is being executed, but is being blocked somewhere
-    in the system.
+    in the system.  To keep the reporting overhead low, the system does not
+    attempt to synchronize different aspects of activity data for a backend.
+    As a result, ephemeral discrepancies may exist between the view's columns.
    </para>
   </note>
 


[parent: 9469d7fdd2bc]