| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Dan Gorman <dgorman(at)hi5(dot)com>, mischa(at)ca(dot)sophos(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Selects query stats? |
| Date: | 2006-05-23 21:47:16 |
| Message-ID: | 1148420837.2755.196.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, 2006-05-23 at 15:55 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > OTOH ISTM it would be easy to modify Postgres so as to count statements
> > in the stat collector, by turning pgstat_report_activity into a routine
> > that sent a count (presumably always 1) instead of the query string, and
> > then just add the count to a counter on receiving.
>
> You wouldn't have to change the backends at all, just modify the
> collector to count the number of report_activity messages received.
> Might have to play some games with ignoring "<IDLE>" messages, but
> otherwise simple (and simplistic...)
The OP wanted statements/sec rather than just a total.
Having stats logged by time would be very useful, but I wouldn't limit
that just to numbers of statements in each time period.
stats_logging_interval = 60 by default, 0 to disable, range 5-3600
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mischa Sandberg | 2006-05-23 22:18:49 | Re: Selects query stats? |
| Previous Message | Guillaume Smet | 2006-05-23 20:04:36 | Re: Selects query stats? |