X-Original-To: pgsql-hackers-pitr-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 493A4D1D643 for ; Tue, 17 Feb 2004 00:07:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 40881-09 for ; Mon, 16 Feb 2004 20:07:53 -0400 (AST) Received: from cmailg5.svr.pol.co.uk (cmailg5.svr.pol.co.uk [195.92.195.175]) by svr1.postgresql.org (Postfix) with ESMTP id F0737D1D501 for ; Mon, 16 Feb 2004 20:07:49 -0400 (AST) Received: from modem-3521.leopard.dialup.pol.co.uk ([217.135.157.193] helo=LaptopDellXP) by cmailg5.svr.pol.co.uk with esmtp (Exim 4.14) id 1AssmG-0002jY-Fz; Tue, 17 Feb 2004 00:07:52 +0000 Reply-To: From: "Simon Riggs" To: "'Tom Lane'" Cc: Subject: Date: Mon, 16 Feb 2004 23:07:25 -0000 Organization: 2nd Quadrant Message-ID: <000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <9293.1076868784@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/19 X-Sequence-Number: 19 >Tom Lane [mailto:tgl@sss.pgh.pa.us] >Re: [pgsql-hackers-pitr] Proposals for PITR >>"Simon Riggs" writes: >> The general PITR recovery scenario requires: >> A - Take a full database backup >> B - Take regular log file backups >> C - Restore a full backup of a database. > Note that pg_dump has absolutely zero to do with this. The base for a > PITR recovery scenario has to be a physical dump, not a logical dump; > else WAL replay won't work. Yes, I agree, I only included it because it was on the TODO. I'll cut it out of the further thinking on PITR, in case it confuses the issue in design/usage. Regards, Simon