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

Re: Deleting old archived WAL files

From: Jaume Sabater <jsabater(at)linuxsilo(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Deleting old archived WAL files
Date: 2008-10-31 12:12:11
Message-ID: 20560805.1971225455131817.JavaMail.root@zimbra.linuxsilo.net (view raw or flat)
Thread:
Lists: pgsql-admin
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-WAL
http://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"


In response to

Responses

pgsql-admin by date

Next:From: Jaume SabaterDate: 2008-10-31 14:24:09
Subject: Re: Deleting old archived WAL files
Previous:From: Mathias StjernströmDate: 2008-10-31 11:36:23
Subject: Re: how i can restrict databaseusers ?

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