From: | A J <s5aly(at)yahoo(dot)com> |
---|---|
To: | PG Admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Cleanup of same archive used by multiple standbys |
Date: | 2011-08-10 16:53:04 |
Message-ID: | 1312995184.42492.YahooMailNeo@web120019.mail.ne1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)yahoo(dot)com>
To: PG Admin <pgsql-admin(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-08-10 16:53:13 | Re: Cleanup of same archive used by multiple standbys |
Previous Message | A J | 2011-08-10 16:41:25 | Cleanup of same archive used by multiple standbys |