From: Jaume Sabater <jsabater@linuxsilo.net>
To: pgsql-admin@postgresql.org
Subject: Re: Deleting old archived WAL files
Date: Fri, 31 Oct 2008 14:24:09 +0000 (GMT)
Message-ID: <21943248.2001225463049735.JavaMail.root@zimbra.linuxsilo.net> (raw)
In-Reply-To: <20560805.1971225455131817.JavaMail.root@zimbra.linuxsilo.net>
Jaume Sabater wrote:
> So, should I set the archive_command parameter to any of these?
>
> 1. exit 0
> 2. cp %p /dev/null
Just checked and both worked fine. Did 30000 transactions per 10 concurrent clients with pgbench and the pg_xlog/ folder never went beyond the initial size (files were rotated inside pg_xlog/, none archived, no errors in the PostgreSQL log).
I think I'll stick with the "exit 0" one, as the cp would have to read the file (although it would probably be in the cache of the kernel as it was just written?).
Now on how to change the archive_command in runtime without having to modify the postgresql.conf file, if possible... :P
--
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: <21943248.2001225463049735.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