Re: Display individual query in pg_stat_activity

From: Jim Nasby <nasbyj(at)amazon(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Schneider (AWS), Jeremy" <schnjere(at)amazon(dot)com>
Subject: Re: Display individual query in pg_stat_activity
Date: 2020-07-29 19:24:45
Message-ID: b886a78f-a6b2-f1fd-f5be-a6e3b5a89fe7@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/27/20 9:57 AM, Dave Page wrote:
> On Mon, Jul 27, 2020 at 3:40 PM Drouvot, Bertrand <bdrouvot(at)amazon(dot)com
> <mailto:bdrouvot(at)amazon(dot)com>> wrote:
<snip>
>
> When multiple statements are displayed then we don’t know which
> one is currently running.
>
>
> I'm not sure I'd want that to happen, as it could make it much harder
> to track the activity back to a query in the application layer or
> server logs.
>
> Perhaps a separate field could be added for the current statement, or
> a value to indicate what the current statement number in the query is?
Perhaps turn query into text[]. That would make it easy to concatenate
back together if desired.
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2020-07-29 19:52:17 Re: new heapcheck contrib module
Previous Message Justin Pryzby 2020-07-29 18:33:45 Re: [PATCH] Tab completion for VACUUM of partitioned tables