| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | "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-27 14:57:10 |
| Message-ID: | CA+OCxozrKrt=39d_kcnpNmOs=wG+4NFTfTa3jqHNuv=DJj9E+g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
On Mon, Jul 27, 2020 at 3:40 PM Drouvot, Bertrand <bdrouvot(at)amazon(dot)com>
wrote:
> Hi hackers,
>
> I've attached a patch to display individual query in the pg_stat_activity
> query field when multiple SQL statements are currently displayed.
>
> *Motivation:*
>
> 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?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anastasia Lubennikova | 2020-07-27 15:21:06 | Re: [BUG] Error in BRIN summarization |
| Previous Message | Justin Pryzby | 2020-07-27 11:13:52 | Re: display offset along with block number in vacuum errors |