Re: fix log_min_duration_statement logic error

On Sat, 4 Oct 2003, Tom Lane wrote:

> Date: Sat, 04 Oct 2003 15:43:34 -0400
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
> Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Neil Conway <neilc(at)samurai(dot)com>,
> PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
> Subject: Re: [PATCHES] fix log_min_duration_statement logic error
>
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> I would prefer to see the log entries look like
> >>
> >> LOG: query: select * from pg_class;
> >> LOG: duration: nn.nnn msec
>
> > The problem with two lines is that another log message could get between
> > them.
>
> That was true already with log_statement and log_duration as separate
> operations. People use log_pid to deal with it.
Sorry to jump in... the log_pid is NOT ENOUGH where you have more than
30000 connections a day (witch is my case)

There has been discussion as to have 1 Log file/database where are we on
that? Is it dead?
Thanks
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>

--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
6, Chemin d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp(at)pyrenet(dot)fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)