From: Alex Friedman <alexf01@gmail.com>
To: Sami Imseih <samimseih@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Doc: clarify possibility of ephemeral discrepancies between state and wait_event in pg_stat_activity
Date: Sun, 2 Mar 2025 12:42:17 +0200
Message-ID: <3aaaddc1-dda9-4d5f-ade5-312a66c3e83a@gmail.com> (raw)
In-Reply-To: <CAA5RZ0sRyfuKbzFpLLoHp0=WnerXwyvZz+-fvFdMKyQqRZpQug@mail.gmail.com>
References: <8a275154-a654-44b0-ab37-197802f04c7b@gmail.com>
<CAA5RZ0ssBs_x=nbrgOViw+E8gBcG0eLHraid1kH-Eg+rx5wm-w@mail.gmail.com>
<ba25c8f6-eafa-4f6c-a436-5a0824bf9593@gmail.com>
<CAA5RZ0sRyfuKbzFpLLoHp0=WnerXwyvZz+-fvFdMKyQqRZpQug@mail.gmail.com>
> 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
Attachments:v3-0001-Clarify-possibility-of-ephemeral-discrepancies-be.patch (text/plain, 1.2K) download
From 58de88469f6201ae698ee34debcdec028526a72a Mon Sep 17 00:00:00 2001
From: Alex Friedman <alexf01@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.sgmlindex 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alexf01@gmail.com, samimseih@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Doc: clarify possibility of ephemeral discrepancies between state and wait_event in pg_stat_activity
In-Reply-To: <3aaaddc1-dda9-4d5f-ade5-312a66c3e83a@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox