From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Greg Spiegelberg <gspiegelberg@cranel.com>
Cc: PgSQL Performance ML <pgsql-performance@postgresql.org>
Cc: Postgres Admin List <pgsql-admin@postgresql.org>
Subject: Re: [PERFORM] syslog slowing the database?
Date: Wed, 10 Mar 2004 23:09:41 -0500
Message-ID: <15549.1078978181@sss.pgh.pa.us> (raw)
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>
Christopher Kings-Lynne <chriskl@familyhealth.com.au> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, gspiegelberg@cranel.com, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] syslog slowing the database?
In-Reply-To: <15549.1078978181@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox