On Sun, 5 Oct 2003, Rod Taylor wrote: > Date: Sun, 05 Oct 2003 13:05:32 -0400 > From: Rod Taylor <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Tom Lane <[EMAIL PROTECTED]>, Bruce Momjian <[EMAIL PROTECTED]>, > Peter Eisentraut <[EMAIL PROTECTED]>, Neil Conway <[EMAIL PROTECTED]>, > PostgreSQL Patches <[EMAIL PROTECTED]> > Subject: Re: [PATCHES] fix log_min_duration_statement logic error > > > > 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) > > log_pid isn't enough, but log_pid + log_connections certainly is. > > log_connections tells you when a new connection was made, so guessing > isn't required. > > > There has been discussion as to have 1 Log file/database where are we on > > that? Is it dead? > > Well, this wouldn't help either unless you happen to have several not so > active databases that makes for a busy system. > Only that I could give the log file to the customer owning the database(s) that would make my job esier.
Also I'd love to see the log_query being settable per database... -- 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: [EMAIL PROTECTED] ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery) ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org