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 8AC3FD1D25D for ; Fri, 13 Feb 2004 00:48:40 +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 78812-09 for ; Thu, 12 Feb 2004 20:48:41 -0400 (AST) Received: from jinx.internetstaff.com (jinx.internetstaff.com [63.214.174.240]) by svr1.postgresql.org (Postfix) with ESMTP id BB6A1D1CCB1 for ; Thu, 12 Feb 2004 20:48:36 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by jinx.internetstaff.com (Postfix) with ESMTP id 372934BC0AD for ; Thu, 12 Feb 2004 17:48:21 -0700 (MST) Received: from jinx.internetstaff.com ([127.0.0.1]) by localhost (jinx [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 28117-03-14 for ; Thu, 12 Feb 2004 17:48:20 -0700 (MST) Received: from [10.10.4.32] (unknown [65.161.175.240]) by jinx.internetstaff.com (Postfix) with ESMTP id 97ECA4BC0A0 for ; Thu, 12 Feb 2004 17:48:20 -0700 (MST) Subject: Re: Review of last summer's PITR patch From: Cott Lang To: pgsql-hackers-pitr@postgresql.org In-Reply-To: <25856.1076553698@sss.pgh.pa.us> References: <25856.1076553698@sss.pgh.pa.us> Content-Type: text/plain Message-Id: <1076633300.4312.214.camel@blackbox> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Thu, 12 Feb 2004 17:48:20 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at internetstaff.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/8 X-Sequence-Number: 8 On Wed, 2004-02-11 at 19:41, Tom Lane wrote: > Anyway, I'm hoping to see some discussion of what to do next and what > the PITR functionality ought to look like from a user's standpoint. As previously discussed on general ... * WAL files archived to a different location instead of recycling. * The ability to force a WAL log switch to ensure all changes during the backup are flushed to archived logs and copied. * Ability to easily apply WAL logs to a standby database. I'd love be able to take a hot backup of my production database, bring it up on another computer and keep it a log or two behind production by continually copying and applying logs to it. * Although not PITR, on a related note, having the ability to do incremental pg_dumps would be a huge boon for those relying on pg_dumps for backups. * Oracle 10g's Flashback feature is interesting. You can roll the entire database back to a point in time with: > flashback database to '3:00 pm'; I would have to say it's hardly critical. :)