Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 413DD63274F for ; Mon, 12 Jul 2010 08:38:43 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 50848-09 for ; Mon, 12 Jul 2010 11:38:35 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from shrek.krogh.cc (2605ds1-ynoe.0.fullrate.dk [90.184.12.24]) by mail.postgresql.org (Postfix) with ESMTP id 3AEA1632DD7 for ; Mon, 12 Jul 2010 08:38:36 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id 7E87B32BF56 for ; Mon, 12 Jul 2010 13:38:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yb0BzXt+Jt3A for ; Mon, 12 Jul 2010 13:38:30 +0200 (CEST) Received: from [90.184.13.151] (2605ds1-ynoe.2.fullrate.dk [90.184.13.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jesper@krogh.cc) by shrek.krogh.cc (Postfix) with ESMTPSA id 60DB332BD44 for ; Mon, 12 Jul 2010 13:38:30 +0200 (CEST) Message-ID: <4C3AFEB5.8000606@krogh.cc> Date: Mon, 12 Jul 2010 13:38:29 +0200 From: Jesper Krogh User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100528 Thunderbird/3.0.5 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: PostgreSQL PITR - more doubts References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.001 tagged_above=-10 required=5 tests=BAYES_20=-0.001 X-Spam-Level: X-Archive-Number: 201007/187 X-Sequence-Number: 39576 On 2010-07-12 13:23, Jayadevan M wrote: > Hello all, > One doubt about how PostgreSQL PITR works. Let us say I have all the > archived WALs for the past week with > archive_command = 'cp -i %p /home/postgres/archive/%f I took a base backup last night. If I try to recover the server today > after > copying the base backup from yesterday and providing > restore_command = 'cp /home/postgres/archive/%f %p' > does PostgreSQL go through all the past week's archived WALS or > it can figure out that the base backup is from yesterday, so skip > a large number of archived WALs and start only from file xxx ? > Yes, It starts out form "where it needs to". Assuming you did a pg_start_backup() before you did your base backup? -- Jesper