X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 06703D1B4C3 for ; Sun, 14 Mar 2004 16:00:18 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 01734-04 for ; Sun, 14 Mar 2004 12:00:21 -0400 (AST) Received: from fep03-mail.bloor.is.net.cable.rogers.com (fep03-mail.bloor.is.net.cable.rogers.com [66.185.86.73]) by svr1.postgresql.org (Postfix) with ESMTP id BD51CD1B467 for ; Sun, 14 Mar 2004 12:00:14 -0400 (AST) Received: from phlogiston.dydns.org ([65.49.121.67]) by fep03-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20040314160018.MDTG411419.fep03-mail.bloor.is.net.cable.rogers.com@phlogiston.dydns.org> for ; Sun, 14 Mar 2004 11:00:18 -0500 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id CB7083E38; Sun, 14 Mar 2004 11:00:18 -0500 (EST) Date: Sun, 14 Mar 2004 11:00:18 -0500 From: Andrew Sullivan To: PgSQL Performance ML Subject: Re: [ADMIN] syslog slowing the database? Message-ID: <20040314160018.GB1400@phlogiston.dyndns.org> Mail-Followup-To: PgSQL Performance ML References: <404E2937.4060604@cranel.com> <370.1078877805@sss.pgh.pa.us> <404F3996.2070105@cranel.com> <7688.1078937631@sss.pgh.pa.us> <404FC23E.9000207@familyhealth.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <404FC23E.9000207@familyhealth.com.au> User-Agent: Mutt/1.5.5.1+cvs20040105i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep03-mail.bloor.is.net.cable.rogers.com from [65.49.121.67] using ID at Sun, 14 Mar 2004 11:00:18 -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/185 X-Sequence-Number: 6041 On Thu, Mar 11, 2004 at 09:34:54AM +0800, Christopher Kings-Lynne wrote: > >You could also consider not using syslog at all: let the postmaster > >output to its stderr, and pipe that into a log-rotation program. > > Not an option I'm afraid. PostgreSQL just jams and stops logging after > the first rotation... Actually, this is what we do. Last year we offered an (admittedly expensive) bespoke log rotator written in Perl for just this purpose. It was rejected on the grounds that it didn't do anything Apache's rotator didn't do, so I didn't pursue it. I'm willing to put it up on gborg, though, if anyone thinks it'll be worth having around. FWIW, we use ours in production. A -- Andrew Sullivan | ajs@crankycanuck.ca The plural of anecdote is not data. --Roger Brinner