| From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: query_id, pg_stat_activity, extended query protocol |
| Date: | 2024-05-15 18:36:23 |
| Message-ID: | D2DBEEEC-8CB0-4948-96ED-B0D1658767BE@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Okay, that's what I precisely wanted to understand: queryId doesn't have
> semantics to show the job that consumes resources right now—it is mostly
> about convenience to know that the backend processes nothing except
> (probably) this query.
It may be a good idea to expose in pg_stat_activity or a
supplemental activity view information about the current state of the
query processing. i.e. Is it parsing, planning or executing a query or
is it processing a nested query.
I can see this being useful and perhaps could be taken up in a
separate thread.
Regards,
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-05-15 18:39:47 | Re: [PATCH] Add --syntax to postgres for SQL syntax checking |
| Previous Message | Robert Haas | 2024-05-15 18:31:00 | Re: Support a wildcard in backtrace_functions |