| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | legrand legrand <legrand_legrand(at)hotmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: nested queries vs. pg_stat_activity |
| Date: | 2020-08-10 20:21:10 |
| Message-ID: | CA+TgmoaM0ME6ESu5rFgkz0g9Z-BLox5_+d8s328Xgn3r_LaGGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 10, 2020 at 4:09 PM Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Would it even solve the problem for them? pg_stat_statements collects aggregate stats and not a view of what's happening right now -- so it'd be mixing two different types of values. And it would get worse if the same thing is executed multiple times concurrently.
True. You could find that you have a queryId that had already been
evicted from the table.
I think it's better to look for a more direct solution to this problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2020-08-10 20:41:42 | Re: autovac issue with large number of tables |
| Previous Message | Robert Haas | 2020-08-10 20:20:21 | Re: Allow some recovery parameters to be changed with reload |