Re: [PROPOSAL] timestamp informations to pg_stat_statements - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PROPOSAL] timestamp informations to pg_stat_statements
Date
Msg-id 9278.1468797341@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PROPOSAL] timestamp informations to pg_stat_statements  (Peter Geoghegan <pg@heroku.com>)
Responses Re: [PROPOSAL] timestamp informations to pg_stat_statements  (Peter Geoghegan <pg@heroku.com>)
Re: [HACKERS] [PROPOSAL] timestamp informations to pg_stat_statements  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Peter Geoghegan <pg@heroku.com> writes:
> On Sun, Jul 17, 2016 at 12:22 AM, Jun Cheol Gim <dialogbox@gmail.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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [PROPOSAL] timestamp informations to pg_stat_statements
Next
From: Tom Lane
Date:
Subject: Re: Obsolete comment within fmgr.c