| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Jun Cheol Gim <dialogbox(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] timestamp informations to pg_stat_statements |
| Date: | 2016-07-17 23:15:41 |
| Message-ID: | 9278.1468797341@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)heroku(dot)com> writes:
> On Sun, Jul 17, 2016 at 12:22 AM, Jun Cheol Gim <dialogbox(at)gmail(dot)com> wrote:
>> If we have timestamp of first and last executed, we can easily gather thess
>> informations and there are tons of more use cases.
> -1 from me.
> I think that this is the job of a tool that aggregates things from
> pg_stat_statements. It's unfortunate that there isn't a good
> third-party tool that does that, but there is nothing that prevents
> it.
The concern I've got about this proposal is that the results get very
questionable as soon as we start dropping statement entries for lack
of space. last_executed would be okay, perhaps, but first_executed
not so much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-07-17 23:18:58 | Re: Obsolete comment within fmgr.c |
| Previous Message | Peter Geoghegan | 2016-07-17 23:06:41 | Re: [PROPOSAL] timestamp informations to pg_stat_statements |