On 1/13/06, Jim C. Nasby <jnasby@pervasive.com> wrote:
> On Thu, Jan 12, 2006 at 10:36:39AM -0800, Joshua D. Drake wrote:
> > Mikael Carneholm wrote:
> > >>In terms of statistics we do have statistics and exhaustive logging that
> > >>can provide you with all of that information. Is there something
> > >>specific that
> > >>the information already provided really doesn't give you?
> > >
> > >Can you give an example query for "list all queries executed since 12.00
> > >AM, order by block_reads desc"? What I'm aiming for
> > >is the ability to turn "measuring" on, regression test my application,
> > >turn "measuring" off again, and list the most offensive queries executed
> > >during the regression test. I know of at least one other DBMS that is
> > >capable of this...won't mention which one :)
> >
> > You can use timestamp and one of the duration logging options for this.
>
> But AFAIK that won't provide any information on IO used, or even blocks
> read. Not to mention that parsing the logs is a PITA.
>
There has been announce recently about a project for analizing slow queries:
http://archives.postgresql.org/pgsql-announce/2006-01/msg00007.php
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)