Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1ToHYw-0007gI-5o for pgsql-admin@arkaria.postgresql.org; Thu, 27 Dec 2012 17:48:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1ToHYv-0002Bt-Kh for pgsql-admin@arkaria.postgresql.org; Thu, 27 Dec 2012 17:48:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1ToHYu-0002Ap-0x for pgsql-admin@postgresql.org; Thu, 27 Dec 2012 17:48:08 +0000 Received: from cmailc.vita.virginia.gov ([166.67.65.183]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1ToHYl-0001Wz-Pe for pgsql-admin@postgresql.org; Thu, 27 Dec 2012 17:48:07 +0000 X-SBRS: None X-HAT: Group: RELAYLIST_WHITELIST, Policy: $RELAYED_WHITELIST X-IronPort-AV: E=Sophos;i="4.84,363,1355115600"; d="scan'208,217";a="298153215" Received: from unknown (HELO COVMSGCES-HUB03.cov.virginia.gov) ([10.192.2.219]) by CRelayC.vita.virginia.gov with ESMTP; 27 Dec 2012 12:47:56 -0500 Received: from COVMSGCES-MBX01.cov.virginia.gov ([10.192.2.206]) by COVMSGCES-HUB03.cov.virginia.gov ([10.192.2.219]) with mapi id 14.02.0318.004; Thu, 27 Dec 2012 12:47:56 -0500 From: "Burgholzer, Robert (DEQ)" To: "pgsql-admin@postgresql.org" Subject: Re: safe to clear pg_xlog archive status directory? Thread-Topic: [ADMIN] safe to clear pg_xlog archive status directory? Thread-Index: Ac3kUhONYbczAFHaQ3y9p6Sm85uQIwAAUoLQAAG3ZkA= Date: Thu, 27 Dec 2012 17:47:56 +0000 Message-ID: <77F5F8FA4B407F43BFCFD3FC347896913CAB97@COVMSGCES-MBX01> References: <77F5F8FA4B407F43BFCFD3FC347896913CAB40@COVMSGCES-MBX01> <128EC501EB29514B87952686265BB9A50C7922@ORD2MBX02G.mex05.mlsrvr.com> In-Reply-To: <128EC501EB29514B87952686265BB9A50C7922@ORD2MBX02G.mex05.mlsrvr.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.211.198] Content-Type: multipart/alternative; boundary="_000_77F5F8FA4B407F43BFCFD3FC347896913CAB97COVMSGCESMBX01_" MIME-Version: 1.0 X-Pg-Spam-Score: -4.2 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --_000_77F5F8FA4B407F43BFCFD3FC347896913CAB97COVMSGCESMBX01_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 c= ourse, 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-pgbasebac= kup.html). This will copy the running master to the slave, and assuming th= e 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 le= d (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 proces= s 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_sta= tus/*" 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 --_000_77F5F8FA4B407F43BFCFD3FC347896913CAB97COVMSGCESMBX01_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Sorry - this was meant= for the list:

Kris,

Thanks for the respons= e 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 ge= t 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 t= ask of upgrading.

 

Does my process, thoug= h obviously cumbersome, sound perilous?

 

Thanks again,

r.b.=

 

 

From: pgsql-ad= min-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 s= yncing the master to the slave, it would be better to use pg_basebackup (h= ttp://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 almos= t immediately.

 

From: pgsql-ad= min-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 r= unning.  I have fumbled a bit, including having a non responsive stand= by 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 en= vision (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, wi= th 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 m= ode

#6 – re-enable archiving on the master and res= tart the postmaster

 

Thanks in advance,

r.b.

 

Robert  Burgholzer

Surface Water Modeler
Virginia DEQ Office of Surface and Ground Water Supply

804-869-3066

 

--_000_77F5F8FA4B407F43BFCFD3FC347896913CAB97COVMSGCESMBX01_--