discrepancy will look like. What about we do something much more
simplified, such
as the below:
"""
To keep the reporting overhead low, the system does not attempt to synchronize
activity data for a backend. As a result, ephemeral discrepancies may
exist between
the view’s columns.
"""
Yes, I believe it makes sense to make it more generic. Attached v3 with a slight
tweak:
+ 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.
Best regards,
Alex Friedman
From 58de88469f6201ae698ee34debcdec028526a72a Mon Sep 17 00:00:00 2001
From: Alex Friedman <alex...@gmail.com>
Date: Wed, 26 Feb 2025 19:59:59 +0200
Subject: [PATCH v3] Clarify possibility of ephemeral discrepancies between
state and wait_event in pg_stat_activity.
---
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 9178f1d34ef..0e34b3509b8 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -1016,7 +1016,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>
--
2.41.0
