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

From Andrew Dunstan
Subject Re: fix log_min_duration_statement logic error
Date
Msg-id 3F6F2826.9020708@dunslane.net
Whole thread Raw
In response to Re: fix log_min_duration_statement logic error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:

>Neil Conway <neilc@samurai.com> writes:
>
>
>>I also don't particularly like the format of the log message (for one
>>thing, the "duration_statement" prefix in the log message shouldn't
>>include an underscore, it's not a variable or anything -- and the case
>>can be made that if we printed the duration because log_duration is set,
>>we don't need to print it again if the duration of the query exceeded
>>log_min_duration_statement), but I haven't changed it.
>>
>>
>
>I think there should be just one "duration: nnn" log entry, printed if
>either condition holds.
>
>
>
I think that would be consistent with my session-end log patch.

cheers

andrew


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: fix log_min_duration_statement logic error
Next
From:
Date:
Subject: bug in clusterdb script