Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vp3Ng-0004Pu-H5 for pgsql-admin@arkaria.postgresql.org; Fri, 06 Dec 2013 21:56:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Vp3Ng-0003U4-1I for pgsql-admin@arkaria.postgresql.org; Fri, 06 Dec 2013 21:56:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vp3Nf-0003Ty-AA for pgsql-admin@postgresql.org; Fri, 06 Dec 2013 21:56:15 +0000 Received: from smtp.01.com ([199.36.142.181]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vp3Nc-0002cm-Qq for pgsql-admin@postgresql.org; Fri, 06 Dec 2013 21:56:14 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id D27FF3F4142; Fri, 6 Dec 2013 15:56:11 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ny-h0lE01Ys; Fri, 6 Dec 2013 15:56:11 -0600 (CST) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id A08B73F42DF; Fri, 6 Dec 2013 15:56:11 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 855213F4305; Fri, 6 Dec 2013 15:56:11 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hrcsNP981Zgd; Fri, 6 Dec 2013 15:56:11 -0600 (CST) Received: from [10.10.10.5] (8.202-62-69.ftth.swbr.surewest.net [69.62.202.8]) by smtp-out-1.01.com (Postfix) with ESMTPSA id E66DD3F4142; Fri, 6 Dec 2013 15:56:10 -0600 (CST) Message-ID: <52A247F9.9060703@pgexperts.com> Date: Fri, 06 Dec 2013 13:56:09 -0800 From: Jeff Frost Organization: PostgresSQL Experts, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Denish Patel CC: Craig James , Payal Singh , "pgsql-admin@postgresql.org" Subject: Re: Cold backup with rsync -- WAL files? References: <52A2425C.7020105@pgexperts.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) 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 On 12/06/13 13:40, Denish Patel wrote: > Jeff, > > If you remove pg_xlogs, I do not expect Postgres to come back! > > I think Craig is referring to WAL files , not pg_xlogs. He is still going to > take backup of pg_xlogs under $PGDATA when Postgres is still down. > > I think there is some misunderstanding here! > I think the misunderstanding might be that you mean *archived* WAL files, and I mean WAL files in the PGDATA directory. I think the latter is what the OP means, but I'm not certain. So, no, you do not need archiving enabled to take a cold backup, but you do need all the WAL files from the pg_xlog directory per mine and Kevin's quick test. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin