Re: Empty query_id in pg_stat_activity

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: zhouenbing <zhouenbing(at)sunwoda-evb(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Empty query_id in pg_stat_activity
Date: 2025-08-14 11:09:38
Message-ID: 202508141109.o32twyl4dbjo@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2025-Aug-13, zhouenbing wrote:

> I see that the Message ID is' ae6ef509-7bba-4d5b-aac4-82def6797e61(at)ewie(dot)name
> The email states that the bug with an empty query_id has been fixed in
> versions 14.14/15.9/16.5/17.1. However, when I tested versions
> 15.4/15.9/17.4 using the pebench-M=simple | extended tool, I still
> encountered the issue of an empty query_id. This has caused some related
> problems in tracking performance issues on Postgres. Is this a testing
> problem or is the bug indeed present?

I think you would have to show a concrete example of what you're talking
about.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dilip Kumar 2025-08-14 11:34:02 Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
Previous Message Dilip Kumar 2025-08-14 11:02:29 Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database