Date: Fri, 6 Dec 2024 16:44:29 +0100
From: Erik Wienhold <ewie@ewie.name>
To: Costa Alexoglou <costa@dbtune.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: Empty query_id in pg_stat_activity
Message-ID: <ae6ef509-7bba-4d5b-aac4-82def6797e61@ewie.name>
References: <CAJ+5Ff4sLuTMpg__fZH67UdaC2bWpLK1U3a8kkj_BvqO8ScYQw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJ+5Ff4sLuTMpg__fZH67UdaC2bWpLK1U3a8kkj_BvqO8ScYQw@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/ae6ef509-7bba-4d5b-aac4-82def6797e61%40ewie.name>
Precedence: bulk

On 2024-12-06 15:32 +0100, Costa Alexoglou wrote:
> Hey folks, I am running Benchbase and pgbench at the same time just for
> debugging purposes, and I notice that sometimes query_id is missing
> from pg_stat_activity. Any clue why this is happening?

What's your Postgres version?

Could be that query_id is not reported because the session is using the
extended query protocol.  This has been fixed just recently in releases
14.14/15.9/16.5/17.1.  From the 14.14 release notes:

> * Report the active query ID for statistics purposes at the start of
>   processing of Bind and Execute protocol messages (Sami Imseih)
>   https://postgr.es/c/b36ee879c
>
>   This allows more of the work done in extended query protocol to be
>   attributed to the correct query.

Another possibility is that the session just disabled compute_query_id:
https://postgr.es/m/472115375.225506.1683812791906%40office.mailbox.org

-- 
Erik