Re: log_min_duration_statement feature - Mailing list pgsql-patches

From Christopher Kings-Lynne
Subject Re: log_min_duration_statement feature
Date
Msg-id 035501c3093a$1aacc7f0$6500a8c0@fhp.internal
Whole thread Raw
In response to log_min_duration_statement feature  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: log_min_duration_statement feature  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
> Yes.  Consider declaring the "max value" in the GUC variable's info block
> as INT_MAX/1000 instead of INT_MAX.
>
> (We should go through all of the GUC variables with an eye to places
> where the max value is unrealistically high, but for the moment I'll
> settle for not introducing any new sillinesses ...)

OK, actually would it make more sense to just make it so that the duration
threshold is given in microseconds instead of milliseconds?  Then I wouldn't
have to multiply and people can threshold lower as well...?

Chris


pgsql-patches by date:

Previous
From: Michael Graff
Date:
Subject: Re: IPv6 address parsing for inet/cidr types (take II)
Next
From: Bruce Momjian
Date:
Subject: Re: log_min_duration_statement feature