Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id C33C3B5DBD6 for ; Wed, 10 Aug 2011 13:53:11 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 78728-08 for ; Wed, 10 Aug 2011 16:53:05 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm29-vm4.bullet.mail.ne1.yahoo.com (nm29-vm4.bullet.mail.ne1.yahoo.com [98.138.91.189]) by mail.postgresql.org (Postfix) with SMTP id 2CD35B5DBCA for ; Wed, 10 Aug 2011 13:53:05 -0300 (ADT) Received: from [98.138.90.53] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2011 16:53:04 -0000 Received: from [98.138.89.197] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2011 16:53:04 -0000 Received: from [127.0.0.1] by omp1055.mail.ne1.yahoo.com with NNFMP; 10 Aug 2011 16:53:04 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 213677.26697.bm@omp1055.mail.ne1.yahoo.com Received: (qmail 74039 invoked by uid 60001); 10 Aug 2011 16:53:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1312995184; bh=kTazc1ppVLbPtcfCf1OcaCpj9aohxVXOMDDC1zSatis=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=2FnnSDzgwbh26labuoCaeEtP/ojGj4fxZklj/eTK+9Q1lp+sr7BmtckcPBaB68IO6kzdALfByMCJQH88l7P3gKAJAII2tPKsdkJ2zBFFjA6XaBkB30yUSYzBxj75D/4khviyKkcNhKro32kbGTgiNorY0z15+VB7srHoALNKbX4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=XeyYxCOWbGpqC3ldoIThSSvjB6D0TYTT54WJS3Bo8epd9qR/Xb/Fhl3qXVpMMal7YpjH93j2rF7CnM0FSODXkAg6wOmIIxJI7QyObq5dwy519JvPB0BD4laMUdZ3mk3yzoms/PSSNGPNPE6+/jhWDvUumnMnkrdnxKfRYnI2cps=; X-YMail-OSG: gNIZKucVM1nUTER2a3ObSnLw30xKGo2WoCw8HgVPBuuYMWF ..CCe.dyM7b13Ou7a6tFIKfVhRDbItvqXmKANAox7Pqb4OKJebVhgtsjJkOj eZcFlWG9sgRrIDy2YKkKH6mRyuP7GpI1RXz3Xl1eU3cEdR7V7R_lgiRJkt1O WkSBUJG8ifm8D506yqlJCXsRg3PYPeBoIIJloYegAM1lqyOYxTuPsToHM2aY PbgO9hfuKBwmi44lDPZZa.99FotpQ.OWuxrhvfcUV2gdApqrp2repsIzLRKq dlan_K1sLH_R2jRIIkpdPRhDEzQRztayTfvfyH7bczSvdseL6LpWQO77F17A i_LDzM74yqiGOSvk6iLoNCG1ooO21aUQJ Received: from [64.61.91.74] by web120019.mail.ne1.yahoo.com via HTTP; Wed, 10 Aug 2011 09:53:04 PDT X-Mailer: YahooMailWebService/0.8.113.313619 References: <1312994485.73719.YahooMailNeo@web120017.mail.ne1.yahoo.com> Message-ID: <1312995184.42492.YahooMailNeo@web120019.mail.ne1.yahoo.com> Date: Wed, 10 Aug 2011 09:53:04 -0700 (PDT) From: A J Reply-To: A J Subject: Re: Cleanup of same archive used by multiple standbys To: PG Admin In-Reply-To: <1312994485.73719.YahooMailNeo@web120017.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-771552871-1859406214-1312995184=:42492" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.709 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.811 X-Spam-Level: X-Archive-Number: 201108/81 X-Sequence-Number: 38068 ---771552871-1859406214-1312995184=:42492 Content-Type: text/plain; charset=us-ascii Also couple of additional related question: 2. Am I correct in my assumption that if for some reason archive is not cleaned up and runs out of space, the WALs will accumulate in pg_xlog directory on the primary. If pg_xlog was to then run out of space, Primary server will stop accepting new writes and fail ? 3. If my standbys are in different datacenter, what is the suggested location of the archive directory ? Is it recommended to have it local in the data center of the primary server or somehow have it over in the remote data center. Thanks for any pointers. ________________________________ From: A J To: PG Admin Sent: Wednesday, August 10, 2011 12:41 PM Subject: Cleanup of same archive used by multiple standbys What is the suggested technique for cleaning up an archive location shared by multiple standbys. Looks like pg_archivecleanup cannot be used as %r refers to last restartpoint of only a single standby server. Do I need to create a custom script that somehow determines the latest common restartpoint of ALL the standbys and then manually run pg_archivecleanup with that value ? Thanks. ---771552871-1859406214-1312995184=:42492 Content-Type: text/html; charset=us-ascii
Also couple of additional related question:
2. Am I correct in my assumption that if for some reason archive is not cleaned up and runs out of space, the WALs will accumulate in pg_xlog directory on the primary. If pg_xlog was to then run out of space, Primary server will stop accepting new writes and fail ?

3. If my standbys are in different datacenter, what is the suggested location of the archive directory ? Is it recommended to have it local in the data center of the primary server or somehow have it over in the remote data center.

Thanks for any pointers.

From: A J <s5aly@yahoo.com>
To: PG Admin <pgsql-admin@postgresql.org>
Sent: Wednesday, August 10, 2011 12:41 PM
Subject: Cleanup of same archive used by multiple standbys

What is the suggested technique for cleaning up an archive location shared by multiple standbys. Looks like pg_archivecleanup cannot be used as %r refers to last restartpoint of only a single standby server.
Do I need to create a custom script that somehow determines the latest common restartpoint of ALL the standbys and then manually run pg_archivecleanup with that value ?

Thanks.


---771552871-1859406214-1312995184=:42492--