Re: [PROPOSAL] timestamp informations to pg_stat_statements

From: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>, Jun Cheol Gim <dialogbox(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PROPOSAL] timestamp informations to pg_stat_statements
Date: 2016-07-17 23:43:32
Message-ID: c124cfb7-a89a-322e-6809-a18066c87265@dalibo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18/07/2016 01:06, Peter Geoghegan wrote:
> 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.
>

FWIW there's https://github.com/dalibo/powa-archivist which does that,
assuming you're using a 9.4+ server.

--
Julien Rouhaud
http://dalibo.com - http://dalibo.org

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-07-18 01:28:00 Re: One process per session lack of sharing
Previous Message Jan Wieck 2016-07-17 23:35:10 Re: DO with a large amount of statements get stuck with high memory consumption