| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: fix log_min_duration_statement logic error |
| Date: | 2003-09-22 16:49:42 |
| Message-ID: | 3F6F2826.9020708@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane wrote:
>Neil Conway <neilc(at)samurai(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | washingtonirving | 2003-09-22 19:15:16 | bug in clusterdb script |
| Previous Message | Tom Lane | 2003-09-22 16:34:12 | Re: fix log_min_duration_statement logic error |