X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 976EFD1CCAD; Thu, 11 Mar 2004 01:37:56 +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 55026-06; Wed, 10 Mar 2004 21:37:58 -0400 (AST) Received: from dnscache2.syd.nexon.com.au (dnscache2.syd.nexon.com.au [210.215.48.100]) by svr1.postgresql.org (Postfix) with ESMTP id 36A90D1CAD9; Wed, 10 Mar 2004 21:37:53 -0400 (AST) Received: from chris ([210.215.130.98]) by dnscache2.syd.nexon.com.au (8.12.8p1/8.12.8) with ESMTP id i2AMaf9g039982; Thu, 11 Mar 2004 09:36:42 +1100 (EST) (envelope-from chris@interspire.com) From: "Chris Smith" To: "'Christopher Kings-Lynne'" Cc: "'PgSQL Performance ML'" , "'Postgres Admin List'" Subject: Re: [PERFORM] syslog slowing the database? Date: Thu, 11 Mar 2004 12:37:38 +1100 Message-ID: <000201c40709$70e5e070$0d00a8c0@chris> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal In-Reply-To: <404FC23E.9000207@familyhealth.com.au> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/214 X-Sequence-Number: 12783 It might depend on how you're rotating it. Try the copy/truncate method instead of moving the log file. If you move the log file to another filename you usually have to restart the app doing the logging before it starts logging again. Chris. -----Original Message----- From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Christopher Kings-Lynne Sent: Thursday, March 11, 2004 12:35 PM To: Tom Lane Cc: Greg Spiegelberg; PgSQL Performance ML; Postgres Admin List Subject: Re: [PERFORM] [ADMIN] syslog slowing the database? > You could also consider not using syslog at all: let the postmaster > output to its stderr, and pipe that into a log-rotation program. I > believe some people use Apache's log rotator for this with good > results. Not an option I'm afraid. PostgreSQL just jams and stops logging after the first rotation... I've read in the docs that syslog logging is the only "production" solution... Chris ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)