Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X9ttm-00027K-2e for pgsql-admin@arkaria.postgresql.org; Wed, 23 Jul 2014 10:35:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X9ttl-0004Lh-Iu for pgsql-admin@arkaria.postgresql.org; Wed, 23 Jul 2014 10:35:49 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X9ttk-0004La-Mg for pgsql-admin@postgresql.org; Wed, 23 Jul 2014 10:35:48 +0000 Received: from mail-yh0-x231.google.com ([2607:f8b0:4002:c01::231]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X9tth-0007GL-KS for pgsql-admin@postgresql.org; Wed, 23 Jul 2014 10:35:47 +0000 Received: by mail-yh0-f49.google.com with SMTP id b6so637381yha.8 for ; Wed, 23 Jul 2014 03:35:44 -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=GG4QyYVBvg6T8paf7UGz7NMkUB+2Uyn0FLbjXHSwrO4=; b=Yjya+KvzC6Xt0v84VqRIGYpRV0XQJIzUS43eTr0qyK7d8gaIWeUsaU5gQ8Y+p+4eTs UtQ4xlyUzoE60Q1vnZpA1HOjyRKmGygph2rc5fJR0tckgvmBvEJd3CauVmLkPPr1zcvb AJe2CurR3zrRlzYK/Ok15Q6xZ/sKgGW8isMnlBrwUgZUAgrFrjJ6VHuwLv99suOM42P2 p6dpKIu/qpMIgT90OLWdJDCCySI+rI9rgDKPnSALp80Cp6UliuPvYk+PMw2IyF3Z6iwq 3FjhJXybrOzi5kELnSxHd0jwpbd8LmP6VlliV7fkf5+mh5FvtcfkB//fPIa+fgod/MhZ 8aqw== X-Received: by 10.236.148.209 with SMTP id v57mr462520yhj.140.1406111744584; Wed, 23 Jul 2014 03:35:44 -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 d58sm6626932yhf.2.2014.07.23.03.35.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jul 2014 03:35:44 -0700 (PDT) References: <53CEB312.5060503@gmail.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <69807615-A0F2-43BB-9CF2-6845030457ED@gmail.com> Cc: "pgsql-admin@postgresql.org" X-Mailer: iPad Mail (11D257) From: jayknowsunix@gmail.com Subject: Re: When is it safe to remove recovery.done? Date: Wed, 23 Jul 2014 06:35:42 -0400 To: Albe Laurenz X-Pg-Spam-Score: -2.0 (--) 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 That's what I was thinking. Thanks. Sent from my iPad > On Jul 23, 2014, at 5:19 AM, Albe Laurenz wrote: >=20 > John Scalia wrote: >> After successfully testing a failover between my primary and a standby s= erver, the old recovery.conf >> file is renamed recovery.done. As this system is now the master, I don't= see a >> need to keep that file around, but is it safe to remove it now? >=20 > It is safe to remove the file, but it doesn't hurt if you keep it (it may= serve as > documentation of your latest recovery). >=20 > Yours, > Laurenz Albe --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin