Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X9fBa-00068G-Dv for pgsql-admin@arkaria.postgresql.org; Tue, 22 Jul 2014 18:53:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X9fBZ-0000N9-UZ for pgsql-admin@arkaria.postgresql.org; Tue, 22 Jul 2014 18:53:13 +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 1X9fBY-0000N0-M9 for pgsql-admin@postgresql.org; Tue, 22 Jul 2014 18:53:13 +0000 Received: from mail-yk0-x22a.google.com ([2607:f8b0:4002:c07::22a]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X9fBU-0006X8-Ui for pgsql-admin@postgresql.org; Tue, 22 Jul 2014 18:53:10 +0000 Received: by mail-yk0-f170.google.com with SMTP id 9so56224ykp.15 for ; Tue, 22 Jul 2014 11:53:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=MMFpqHvnvPoQkU5Tb3TwstdMGN2xsAp1SlD/7dip3wM=; b=W7/nlzb4WOpYixLhVCBCP6jtQD9zpfmbRUIoNdxig91Ka06aR0WCeq2DCDFPnk1DQh 9MY39xL1VYSneyPiG7Mv0pc+dhIFHFMClnGJahYIh+HwRxnpVEyOcBT84/OGPXOc2G4C If/sgOfyN5C1ujxFKcPpE/QBWhGZ5t6648RIpa5Y0AI3PfJl7tUECp2MRFaNBckloRm6 YAcqEicxelYFkXvkTZ+S9CJL6fAhb0FWt2zfMdRgrf9E82G3fRVxZyuqqR8D4C1eldMm taBfiG/T63mAUNbc7km54kn3tRpmSJqAj8eViLxPA5lNy7i0IYFrvAp56qBOfQi9iCg9 zISA== X-Received: by 10.236.203.33 with SMTP id e21mr53795641yho.92.1406055187807; Tue, 22 Jul 2014 11:53:07 -0700 (PDT) Received: from [192.168.254.6] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id g30sm2340620yhn.46.2014.07.22.11.53.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jul 2014 11:53:07 -0700 (PDT) Message-ID: <53CEB312.5060503@gmail.com> Date: Tue, 22 Jul 2014 14:53:06 -0400 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: When is it safe to remove recovery.done? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 After successfully testing a failover between my primary and a standby server, 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? -- Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin