| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: nested queries vs. pg_stat_activity |
| Date: | 2020-08-10 19:51:03 |
| Message-ID: | CA+TgmoZET4hz+p9VMQG3OX3SGJWw8dbKKu0KbMdpC7eWfossrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 10, 2020 at 12:51 PM legrand legrand
<legrand_legrand(at)hotmail(dot)com> wrote:
> An other solution is to expose nested queryid, and to join it with pg_stat_statements.
> Actual development trying to add queryid to pg_stat_activity isn't helpfull, because it is only exposing top level one.
> Extension pg_stat_sql_plans (github) propose a function called pg_backend_queryid(pid),
> that gives the expected queryid (that is stored in shared memory for each backend) ...
That'd help people using pg_stat_statements, but not others.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2020-08-10 20:09:41 | Re: nested queries vs. pg_stat_activity |
| Previous Message | Robert Haas | 2020-08-10 19:50:19 | Re: Issue with cancel_before_shmem_exit while searching to remove a particular registered exit callbacks |