From: A J <s5aly@yahoo.com>
To: PG Admin <pgsql-admin@postgresql.org>
Subject: Re: Cleanup of same archive used by multiple standbys
Date: Wed, 10 Aug 2011 09:53:04 -0700 (PDT)
Message-ID: <1312995184.42492.YahooMailNeo@web120019.mail.ne1.yahoo.com> (raw)
In-Reply-To: <1312994485.73719.YahooMailNeo@web120017.mail.ne1.yahoo.com>
References: <1312994485.73719.YahooMailNeo@web120017.mail.ne1.yahoo.com>
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.
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: s5aly@yahoo.com
Subject: Re: Cleanup of same archive used by multiple standbys
In-Reply-To: <1312995184.42492.YahooMailNeo@web120019.mail.ne1.yahoo.com>
* 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