Re: fix log_min_duration_statement logic error - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: fix log_min_duration_statement logic error
Date
Msg-id 200310071656.h97GuZk20298@candle.pha.pa.us
Whole thread Raw
In response to Re: fix log_min_duration_statement logic error  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: fix log_min_duration_statement logic error  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Another idea if you like consistency would be:
> >
> >     LOG:  duration: 4.056 ms  query: select * \nfrom pg_language;
>
> Speaking of consistency...
>
> Imagine someone always having log_statement on and doing some sort of
> aggregate query counting, say like grep '^LOG: query:' | wc -l.  Now that
> someone (or maybe the admin on the night shift, to make it more dramatic)
> also turns on log_min_statement_duration (or whatever it's spelled), say
> to find the slowest queries: grep '^LOG: duration:' | sort -xyz | head
> -10.  In order to guarantee the consistency of both results, you'd have to
> log each query twice in this case.

I guess.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: fix log_min_duration_statement logic error
Next
From: Bruce Momjian
Date:
Subject: Re: Bug in pg_restore memory handling