Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42672=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X9fNk-0006tG-KF
 for pgsql-admin@arkaria.postgresql.org; Tue, 22 Jul 2014 19:05:48 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42672=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X9fNj-0004h9-4z
 for pgsql-admin@arkaria.postgresql.org; Tue, 22 Jul 2014 19:05:47 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1X9fNi-0004gz-1u
 for pgsql-admin@postgresql.org; Tue, 22 Jul 2014 19:05:46 +0000
Received: from mail-yh0-x22c.google.com ([2607:f8b0:4002:c01::22c])
 by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1X9fNY-00044u-63
 for pgsql-admin@postgresql.org; Tue, 22 Jul 2014 19:05:44 +0000
Received: by mail-yh0-f44.google.com with SMTP id f73so69728yha.17
 for <pgsql-admin@postgresql.org>; Tue, 22 Jul 2014 12:05:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=references:mime-version:in-reply-to:content-type
 :content-transfer-encoding:message-id:cc:from:subject:date:to;
 bh=PI1sKdFMf5Zu7KMG/F03HHmpu3lkLBrYRlaVz3/9FQc=;
 b=E7lKamm1uc0Mec841pVnwO8p0qh4SPWVZKdUZYDSbw2Zre3JbtGRA7QJH5WBiidZSn
 bKwl/JszNacxoz5UIjVD/1g5ADy8zRVvCLDcWNjaGJABIcngIu8waRvViQM7sqybcovL
 Swy3Jk82oqiim8lRzJeB0oHMFcgUd81HjMmj2UvFB3RT033JHrQHy6aOM+C7HFHAkZX7
 jyAgQpA48od54wRkyvOLbi1FWFs83fnsc7jUn21V7Xi8xnfdjbKUvq5aylFM/peYKISJ
 pTKmxAWGadtw3sqw8WraaEiG1bN+x+SrjkkneJAdQt3tz6O9Lt8ULt99tHHKa7wcAQZp
 nnDg==
X-Received: by 10.236.91.74 with SMTP id g50mr4020022yhf.59.1406055933903;
 Tue, 22 Jul 2014 12:05:33 -0700 (PDT)
Received: from [192.168.254.1] (h77.89.102.166.static.ip.windstream.net.
 [166.102.89.77])
 by mx.google.com with ESMTPSA id j21sm2414693yhj.29.2014.07.22.12.05.33
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Tue, 22 Jul 2014 12:05:33 -0700 (PDT)
References: <53CEB312.5060503@gmail.com>
 <425387904.576712.1406055513880.JavaMail.zimbra@mail.int.journyx.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: 
 <425387904.576712.1406055513880.JavaMail.zimbra@mail.int.journyx.com>
Content-Type: multipart/alternative;
 boundary=Apple-Mail-45F86963-78FF-4A6D-9D67-902F060CE199
Content-Transfer-Encoding: 7bit
Message-Id: <C9E258FA-1A56-48D2-9056-70837D4B012E@gmail.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
X-Mailer: iPad Mail (11D257)
From: jayknowsunix@gmail.com
Subject: Re: When is it safe to remove recovery.done?
Date: Tue, 22 Jul 2014 15:05:33 -0400
To: Scott Whitney <swhitney@journyx.com>
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


--Apple-Mail-45F86963-78FF-4A6D-9D67-902F060CE199
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Well, I do keep a recovery.conf master file in the Postgres home directory o=
n each of the systems. My failover script takes care of copying it up into t=
he data directory, as well as making any required changes to it. (I use two s=
tandby servers, so if the primary fails, one gets promoted and the other mus=
t be repointed.)

Sent from my iPad

> On Jul 22, 2014, at 2:58 PM, Scott Whitney <scott@journyx.com> wrote:
>=20
> Well, it depends on whether or not you need the file.
>=20
> It's renamed so the system doesn't accidentally try to re-enter recovery m=
ode.
>=20
> However if you're still planning on having a standby, you _will_ need a re=
covery.conf file, and that's what this is, just renamed.
>=20
>=20
> After successfully testing a failover between my primary and a standby ser=
ver, the old recovery.conf file is renamed recovery.done. As this system is n=
ow the master, I don't see a=20
> need to keep that file around, but is it safe to remove it now?
> --
> Jay
>=20
>=20
> --=20
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>=20

--Apple-Mail-45F86963-78FF-4A6D-9D67-902F060CE199
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Well, I do keep a recovery.conf master=
 file in the Postgres home directory on each of the systems. My failover scr=
ipt takes care of copying it up into the data directory, as well as making a=
ny required changes to it. (I use two standby servers, so if the primary fai=
ls, one gets promoted and the other must be repointed.)<br><br>Sent from my i=
Pad</div><div><br>On Jul 22, 2014, at 2:58 PM, Scott Whitney &lt;<a href=3D"=
mailto:scott@journyx.com">scott@journyx.com</a>&gt; wrote:<br><br></div><blo=
ckquote type=3D"cite"><div><div style=3D"font-family: times new roman, new y=
ork, times, serif; font-size: 12pt; color: #000000"><div>Well, it depends on=
 whether or not you need the file.<br></div><div><br></div><div>It's renamed=
 so the system doesn't accidentally try to re-enter recovery mode.</div><div=
><br></div><div>However if you're still planning on having a standby, you _w=
ill_ need a recovery.conf file, and that's what this is, just renamed.</div>=
<div><br></div><div><br></div><hr id=3D"zwchr"><blockquote style=3D"border-l=
eft:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weigh=
t:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,=
sans-serif;font-size:12pt;">After successfully testing a failover between my=
 primary and a standby server, the old recovery.conf file is renamed recover=
y.done. As this system is now the master, I don't see a <br>need to keep tha=
t file around, but is it safe to remove it now?<br>--<br>Jay<br><div><br></d=
iv><br>-- <br>Sent via pgsql-admin mailing list (<a href=3D"mailto:pgsql-adm=
in@postgresql.org">pgsql-admin@postgresql.org</a>)<br>To make changes to you=
r subscription:<br><a href=3D"http://www.postgresql.org/mailpref/pgsql-admin=
">http://www.postgresql.org/mailpref/pgsql-admin</a><br></blockquote><div><b=
r></div></div></div></blockquote></body></html>=

--Apple-Mail-45F86963-78FF-4A6D-9D67-902F060CE199--