From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | anand086 <anand086(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_stat_statements -- Historical Query |
Date: | 2017-08-10 04:41:46 |
Message-ID: | CAB7nPqTVMuDjUqVgYB7xrL7g2nwmcstFfVDGHThjyjiZeF9TiA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Aug 10, 2017 at 6:23 AM, anand086 <anand086(at)gmail(dot)com> wrote:
> I was looking for a way to maintain historical query details in Postgres to
> answer questions like
>
> What was the sql call rate between time X and Y?
> Did the execution count increase for the query increase between time X and
> Y?
> In past 10mins what all queries were run in the db?
>
> and few others like this.
>
> What would be best way to do it? Any thoughts?
pg_stat_statements has a function allowing to reset what the view
pg_stat_statements holds as information. You could copy periodically
the data of pg_stat_statements and then invoke
pg_stat_statements_reset to put everything back to zero. Then you
would just need to do your analysis work based on the amount of data
copied into your custom table.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2017-08-10 07:30:54 | Re: pg_stat_statements -- Historical Query |
Previous Message | anand086 | 2017-08-10 04:23:13 | pg_stat_statements -- Historical Query |