Re: [GENERAL] pg_stat_statements -- Historical Query

2017-08-10 Thread Julien Rouhaud
On Thu, Aug 10, 2017 at 3:00 PM, Melvin Davidson wrote: > > If you are interested in historical stats, you would probably fair a lot > better with PgBadger. It is free > and highly customizable. In addition to SQL call rates at different times, > it provides analysis of >

Re: [GENERAL] pg_stat_statements -- Historical Query

2017-08-10 Thread Melvin Davidson
On Thu, Aug 10, 2017 at 3:30 AM, Julien Rouhaud wrote: > On Thu, Aug 10, 2017 at 6:41 AM, Michael Paquier > wrote: > > On Thu, Aug 10, 2017 at 6:23 AM, anand086 wrote: > >> I was looking for a way to maintain historical query

Re: [GENERAL] pg_stat_statements -- Historical Query

2017-08-10 Thread Julien Rouhaud
On Thu, Aug 10, 2017 at 6:41 AM, Michael Paquier wrote: > On Thu, Aug 10, 2017 at 6:23 AM, anand086 wrote: >> I was looking for a way to maintain historical query details in Postgres to >> answer questions like >> >> What was the sql call rate

Re: [GENERAL] pg_stat_statements -- Historical Query

2017-08-09 Thread Michael Paquier
On Thu, Aug 10, 2017 at 6:23 AM, anand086 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

[GENERAL] pg_stat_statements -- Historical Query

2017-08-09 Thread anand086
Hi, 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