Re: log_duration - Mailing list pgsql-hackers

From Tom Lane
Subject Re: log_duration
Date
Msg-id 10231.1045109729@sss.pgh.pa.us
Whole thread Raw
In response to Re: log_duration  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: log_duration
Re: [HACKERS] log_duration
Re: [HACKERS] log_duration
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> One nice thing is that each element is orthoginal.  But, for the
> functionality desired, we have to merge log_statement and log_duration
> and have it print for statements taking over X milliseconds.  I have no
> problem adding it, but it has to be clear it isn't orthoginal but is a
> conditional combination of two other parameters.

Actually, I was wondering if we shouldn't *replace* the current
log_duration with a combined form (that specifies a minimum interesting
duration).  I can't quite see the need for orthogonality here.  The
only reason you'd care about query duration is that you're looking for
the slow ones, no?  So why bother logging the fast ones?  Besides, you
can specify min-duration zero if you really want 'em all.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Kevin Brown
Date:
Subject: Re: log_duration
Next
From: Joe Conway
Date:
Subject: loading libraries on Postmaster startup