pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Smith <chris@interspire.com>
To: 'Christopher Kings-Lynne' <chriskl@familyhealth.com.au>
Cc: 'PgSQL Performance ML' <pgsql-performance@postgresql.org>
Cc: 'Postgres Admin List' <pgsql-admin@postgresql.org>
Subject: Re: [PERFORM] syslog slowing the database?
Date: Thu, 11 Mar 2004 12:37:38 +1100
Message-ID: <000201c40709$70e5e070$0d00a8c0@chris> (raw)
In-Reply-To: <404FC23E.9000207@familyhealth.com.au>

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)





view thread (19+ messages)  latest in thread

Message-ID: <000201c40709$70e5e070$0d00a8c0@chris>
Permalink:  ../000201c40709$70e5e070$0d00a8c0@chris/
Also on:    postgresql.org/message-id/000201c40709$70e5e070$0d00a8c0@chris

 · 

reply

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: chris@interspire.com, chriskl@familyhealth.com.au, pgsql-admin@postgresql.org
  Subject: Re: [PERFORM] syslog slowing the database?
  In-Reply-To: <000201c40709$70e5e070$0d00a8c0@chris>

* 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