Skip site navigation (1) Skip section navigation (2)

Re: Postgres Log Rolling

From: heatherm(at)famoice(dot)com
To: nwalker(at)eldocomp(dot)com, pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres Log Rolling
Date: 2002-02-20 22:11:08
Message-ID: H000007e000956a4.1014243066.server1.workware@MHS (view raw, whole thread or download thread mbox)
Lists: pgsql-admin

We're using Red Hat Linux logrotate to do this
A file we called pgsql is put in the /etc/logrotate.d directory, it's 
contents are as follows
/var/log/pgsql {
    rotate 5
This rotates the log files each morning when the daily cron jobs are 
run. We found copytruncate to be the key, since without it the logs 
weren't rotated.
Hope this helps
Heather Murray.

> -----Original Message-----
> From: nwalker [mailto:nwalker(at)eldocomp(dot)com]
> Sent: Thursday, 21 February 2002 05:47
> To: pgsql-admin
> Cc: nwalker
> Subject: FW: [ADMIN] Postgres Log Rolling
> This should be an easy one, but......
> We need to start rolling our postgres error logs.  I wondered 
> whether or 
> not I could pull the rug out from under postgres by just renaming the 
> pgsql.log to 'date'.log and then recreating (touch pgsql.log) the log.
> I then vacuum'd a database (so it would write stuff in the log), and 
> noticed that the renamed log ('date'.log) was the one written 
> to, not the 
> new pgsql.log.
> Do I have to bounce the cluster to roll the log?   How should I be 
> performing this task?
> --
> Naomi Walker
> Chief Information Officer
> Eldorado Computing, Inc.
> 602-604-3100  ext 242 
> ---------------------------(end of 
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?

pgsql-admin by date

Next:From: Antony StaceDate: 2002-02-21 08:50:34
Subject: Locks on Tables
Previous:From: Stephan SzaboDate: 2002-02-20 21:33:41
Subject: Re: pg_dump and pg_dumpall error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group