Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Date
Msg-id b6b62bd0-be5d-2d01-c4e6-aad5c1d01e89@enterprisedb.com
Whole thread Raw
In response to Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 13.07.21 10:58, Magnus Hagander wrote:
> Maybe "each distinct database id, each distinct user id, each distinct
> query id, and whether it is a top level statement or not"?
> 
> Or maybe "each distinct combination of database id, user id, query id
> and whether it's a top level statement or not"?

Okay, now I understand what is meant here.  The second one sounds good 
to me.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Detecting File Damage & Inconsistencies
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: possibility to read dumped table's name from file