Re: log_min_duration_statement #2

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: log_min_duration_statement #2
Date: 2003-06-01 03:50:15
Message-ID: 200306010350.h513oFC05020@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


Your patch has been added to the PostgreSQL unapplied patches list at:

http://momjian.postgresql.org/cgi-bin/pgpatches

I will try to apply it within the next 48 hours.

I am going to modify your patch slightly. I am going to configure it so
if you set the value to '1', you always get the duration and statement.
As it is coded, a query less than 1 millisecond will not print with a
value of '1', and I am going to document this behavior. I am also going
to remove the mention of the maximum in the docs --- seems unnecessary.

---------------------------------------------------------------------------

Christopher Kings-Lynne wrote:
> OK,
>
> This limits max value to INT_MAX / 1000.
>
> Chris

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-06-01 04:31:13 Re: "Adding missing from clause"
Previous Message Rod Taylor 2003-06-01 03:08:49 Re: [HACKERS] Are we losing momentum?