Re: log_min_duration_statement feature

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: log_min_duration_statement feature
Date: 2003-04-23 01:46:05
Message-ID: 035501c3093a$1aacc7f0$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-04-23 02:31:26 Re: log_min_duration_statement feature
Previous Message Michael Graff 2003-04-22 23:34:57 Re: IPv6 address parsing for inet/cidr types (take II)