Re: Empty query_id in pg_stat_activity

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Erik Wienhold <ewie(at)ewie(dot)name>
Cc: Costa Alexoglou <costa(at)dbtune(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Empty query_id in pg_stat_activity
Date: 2024-12-09 07:48:26
Message-ID: Z1agylwejFs6Yj1T@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Dec 06, 2024 at 04:44:29PM +0100, Erik Wienhold wrote:
> Another possibility is that the session just disabled compute_query_id:
> https://postgr.es/m/472115375.225506.1683812791906%40office.mailbox.org

Or possibly this uses a path where we're not aggressive enough the
query ID while we should know it (there are slight cases where we
could finish without one, like some PL contexts).

If you could provide more details for the reproduction of the problem
that does not involve benchbase, that would save time.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joe Wildish 2024-12-09 11:42:39 pg_upgrade vs. logical replication
Previous Message Will Storey 2024-12-09 00:42:38 Cancelled query due to buffer deadlock with recovery