From: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
Date: | 2019-03-16 18:21:13 |
Message-ID: | 1552760473548-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
This is available in https://github.com/legrandlegrand/pg_stat_sql_plans
extension with a specific function
pgssp_backend_queryid(pid) that permits to join pg_stat_activity with
pg_stat_sql_plans (that is similar to pg_stat_statements) and also permits
to collect samples of wait events per query id.
This extension computes its own queryid based on a normalized query text
(that doesn't change after table
drop/create).
Maybe that queryid calculation should stay in a dedicated extension,
permiting to users to choose their queryid definition.
Regards
PAscal
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2019-03-16 18:38:22 | Re: jsonpath |
Previous Message | Alexander Korotkov | 2019-03-16 18:16:21 | Re: jsonpath |