From: Jaume Sabater <jsabater@linuxsilo.net>
To: pgsql-admin@postgresql.org
Subject: Re: Deleting old archived WAL files
Date: Fri, 31 Oct 2008 12:12:11 +0000 (GMT)
Message-ID: <20560805.1971225455131817.JavaMail.root@zimbra.linuxsilo.net> (raw)
In-Reply-To: <490A1668.6000107@otg-nc.com>
Chander Ganesan wrote:
> Note: If you are using 8.3, you can even just disable the
> archive_command when you aren't doing a recovery...
Hmmm... after reading these pages:
http://www.postgresql.org/docs/8.3/static/continuous-archiving.html#BACKUP-ARCHIVING-WALhttp://www.postgresql.org/docs/8.3/static/runtime-config-wal.html#GUC-ARCHIVE-COMMAND
I understand that, if the archive_command is set to an empty string, then WAL files will accumulate in pg_xlog/ until a working archive_command is re-established.
So, should I set the archive_command parameter to any of these?
1. exit 0
2. cp %p /dev/null
Or something similar. I mean this as I have no intention to preserve them unless I am doing an online recovery, in which case I would actually set a meaningful value into that parameter:
archive_command = '/bin/cp %p /var/lib/postgresql/pg_xlog_archive/%f'
--
Jaume Sabater
http://linuxsilo.net/
"Ubi sapientas ibi libertas"
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-admin@postgresql.org
Cc: jsabater@linuxsilo.net
Subject: Re: Deleting old archived WAL files
In-Reply-To: <20560805.1971225455131817.JavaMail.root@zimbra.linuxsilo.net>
* 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