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

From Peter Eisentraut
Subject Re: fix log_min_duration_statement logic error
Date
Msg-id Pine.LNX.4.44.0310071826240.21517-100000@peter.localdomain
Whole thread Raw
In response to Re: fix log_min_duration_statement logic error  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: fix log_min_duration_statement logic error
List pgsql-patches
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.

--
Peter Eisentraut   peter_e@gmx.net


pgsql-patches by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: fix log_min_duration_statement logic error
Next
From: Bruce Momjian
Date:
Subject: Re: fix log_min_duration_statement logic error