From: Michael Paquier Date: Wed, 26 Mar 2025 23:07:54 +0000 (+0900) Subject: doc: Mention possible ephemeral discrepancies in pg_stat_activity X-Git-Tag: REL_18_BETA1~422 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f056f75dafd0025d26efaca026a87f14c079a130;p=thirdparty%2Fpostgresql.git 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 Reviewed-by: Sami Imseih Discussion: https://postgr.es/m/8a275154-a654-44b0-ab37-197802f04c7b@gmail.com --- 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 waiting on some event. If the state is active and wait_event 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.