Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5563664FD69 for ; Fri, 31 Oct 2008 11:24:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 53121-05 for ; Fri, 31 Oct 2008 11:24:14 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zimbra.linuxsilo.net (zimbra.linuxsilo.net [92.48.122.79]) by postgresql.org (Postfix) with ESMTP id 0C0D2650259 for ; Fri, 31 Oct 2008 11:24:14 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.linuxsilo.net (Postfix) with ESMTP id AEFEA2A2EF for ; Fri, 31 Oct 2008 14:24:12 +0000 (GMT) X-Virus-Scanned: amavisd-new at Received: from zimbra.linuxsilo.net ([127.0.0.1]) by localhost (zimbra.linuxsilo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13XfW1IXNvYj for ; Fri, 31 Oct 2008 14:24:09 +0000 (GMT) Received: from zimbra.linuxsilo.net (zimbra.linuxsilo.net [92.48.122.79]) by zimbra.linuxsilo.net (Postfix) with ESMTP id CE99B2A2EE for ; Fri, 31 Oct 2008 14:24:09 +0000 (GMT) Date: Fri, 31 Oct 2008 14:24:09 +0000 (GMT) From: Jaume Sabater To: pgsql-admin@postgresql.org Message-ID: <21943248.2001225463049735.JavaMail.root@zimbra.linuxsilo.net> In-Reply-To: <20560805.1971225455131817.JavaMail.root@zimbra.linuxsilo.net> Subject: Re: Deleting old archived WAL files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [212.170.239.110] X-Mailer: Zimbra 5.0.10_GA_2609.DEBIAN4.0 (ZimbraWebClient - FF3.0 (Linux)/5.0.10_GA_2609.DEBIAN4.0) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/193 X-Sequence-Number: 30649 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"