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:
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'
"Ubi sapientas ibi libertas"
In response to
pgsql-admin by date
|Next:||From: Jaume Sabater||Date: 2008-10-31 14:24:09|
|Subject: Re: Deleting old archived WAL files|
|Previous:||From: Mathias Stjernström||Date: 2008-10-31 11:36:23|
|Subject: Re: how i can restrict databaseusers ?|