From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dominique Devienne <ddevienne@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: is pg_stat_activity "transactional"? How fast does it update?
In-reply-to: <CAFCRh-8WDkn2N+s43fofR4eKHcJC8fiotqWqSGkDQ4Sh4ZYwDg@mail.gmail.com>
References: <CAFCRh-8WDkn2N+s43fofR4eKHcJC8fiotqWqSGkDQ4Sh4ZYwDg@mail.gmail.com>
Comments: In-reply-to Dominique Devienne <ddevienne@gmail.com>
	message dated "Tue, 10 Jun 2025 14:50:11 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <755974.1749565677.1@sss.pgh.pa.us>
Date: Tue, 10 Jun 2025 10:27:57 -0400
Message-ID: <755975.1749565677@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/755975.1749565677%40sss.pgh.pa.us>
Precedence: bulk

Dominique Devienne <ddevienne@gmail.com> writes:
> So when and how fast does pg_stat_activity update, in the face of a
> PQfinish?

The shared state underlying pg_stat_activity is updated
immediately when something changes.  However ...

PQfinish is asynchronous: it sends a "goodbye" message and then
closes the connection without waiting for a response.  So
depending on system load, the associated backend could still be
alive for some milliseconds.  There might be other client
libraries that do that differently.

Another thing that might be biting you is that a backend inspecting
pg_stat_activity() takes a snapshot of the view's contents and then
holds onto that snapshot until end of transaction.  You can get
around that with pg_stat_clear_snapshot().

			regards, tom lane