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 62EE4D1B4B9; Thu, 11 Mar 2004 04:09:55 +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 05619-03; Thu, 11 Mar 2004 00:09:53 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id BF1F9D1D269; Thu, 11 Mar 2004 00:09:52 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2B49fJU015550; Wed, 10 Mar 2004 23:09:41 -0500 (EST) To: Christopher Kings-Lynne Cc: Greg Spiegelberg , PgSQL Performance ML , Postgres Admin List Subject: Re: [PERFORM] syslog slowing the database? In-reply-to: <404FC23E.9000207@familyhealth.com.au> 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> Comments: In-reply-to Christopher Kings-Lynne message dated "Thu, 11 Mar 2004 09:34:54 +0800" Date: Wed, 10 Mar 2004 23:09:41 -0500 Message-ID: <15549.1078978181@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/196 X-Sequence-Number: 12765 Christopher Kings-Lynne writes: >> 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 know some people use this in production. Dunno what went wrong in your test, but it can be made to work. regards, tom lane