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

From Julien Rouhaud
Subject Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activityview?
Date
Msg-id CAOBaU_YRUnpDh6GV5z+BpxYcaYhZ-s7+C27bSecaEs-7Vx-CHA@mail.gmail.com
Whole thread Raw
In response to Re: Feature improvement: can we add queryId forpg_catalog.pg_stat_activity view?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Thu, Aug 1, 2019 at 10:52 PM Andres Freund <andres@anarazel.de> wrote:
>
> On 2019-08-01 22:42:23 +0200, Julien Rouhaud wrote:
> > Sure, but it requires extra wrapper functions, and the st_changecount
> > dance when writing the new value.
>
> So? You need a wrapper function anyway, there's no way we're going to
> add all those separate pg_atomic_write* calls directly.

Ok

> I also think this proposed column should probably respect
> the track_activities GUC.

Oh indeed, I'll fix that when I'll be sure of the semantics to implement.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Feature improvement: can we add queryId forpg_catalog.pg_stat_activity view?
Next
From: Thomas Munro
Date:
Subject: Re: Speed up transaction completion faster after many relations areaccessed in a transaction