From: Burgholzer, Robert (DEQ) <Robert.Burgholzer@deq.virginia.gov>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: safe to clear pg_xlog archive status directory?
Date: Thu, 27 Dec 2012 17:47:56 +0000
Message-ID: <77F5F8FA4B407F43BFCFD3FC347896913CAB97@COVMSGCES-MBX01> (raw)
In-Reply-To: <128EC501EB29514B87952686265BB9A50C7922@ORD2MBX02G.mex05.mlsrvr.com>
References: <77F5F8FA4B407F43BFCFD3FC347896913CAB40@COVMSGCES-MBX01>
<128EC501EB29514B87952686265BB9A50C7922@ORD2MBX02G.mex05.mlsrvr.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Sorry - this was meant for the list:
Kris,
Thanks for the response and advice. Unfortunately, I am operating on an 8.3 setup, so I do not think that this is available to me. I am trying, of course, to get my head around migrating to the 9.x version, but am a little stuck right now - I need to weather the next month with my current setup (a high data collection period for us) and then tackle the task of upgrading.
Does my process, though obviously cumbersome, sound perilous?
Thanks again,
r.b.
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Kris Bushover
Sent: Thursday, December 27, 2012 12:01 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] safe to clear pg_xlog archive status directory?
Rather than manually syncing the master to the slave, it would be better to use pg_basebackup (http://www.postgresql.org/docs/9.1/static/app-pgbasebackup.html). This will copy the running master to the slave, and assuming the recovery.conf is in place on the slave, it can be restarted into recovery mode almost immediately.
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Burgholzer, Robert (DEQ)
Sent: Thursday, December 27, 2012 10:49 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] safe to clear pg_xlog archive status directory?
I am working through getting a warm standby up and running. I have fumbled a bit, including having a non responsive standby node for a hile, which led (I think) to a big pile of "ready" files in the "pg_xlog/archive_status" directory. My thought is that I need to start fresh, so here is the process that I envision (someone please let me know if I am making mental errors):
#1 - turn off archiving on the master, restart
#2 - shut down postgresql on the replicant
#3 - clear the pg_xlog/archive_status/ dir, with an "rm pg_xlog/archive_status/*" command
#4 - perform a fresh rsync backup of my master to my replicant
#5 - bring my replicant back up into standby mode
#6 - re-enable archiving on the master and restart the postmaster
Thanks in advance,
r.b.
Robert Burgholzer
Surface Water Modeler
Virginia DEQ Office of Surface and Ground Water Supply
804-869-3066
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: Robert.Burgholzer@deq.virginia.gov
Subject: Re: safe to clear pg_xlog archive status directory?
In-Reply-To: <77F5F8FA4B407F43BFCFD3FC347896913CAB97@COVMSGCES-MBX01>
* 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