Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2D88F9FB202 for ; Mon, 8 Jan 2007 12:29:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 46762-05-3 for ; Mon, 8 Jan 2007 12:29:42 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id E4C809FB1F9 for ; Mon, 8 Jan 2007 12:29:41 -0400 (AST) thread-index: AcczQjayytPeXwPqSYCPZZrG1zWYtQ== Received: from [192.168.0.22] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 8 Jan 2007 11:29:47 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 Content-Class: urn:content-classes:message Importance: normal Subject: Re: PITR recovery From: "Simon Riggs" To: "Ben K." Cc: In-Reply-To: References: <1168097862.3655.249.camel@silverbirch.site> Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 08 Jan 2007 16:28:45 +0000 Message-ID: <1168273726.3951.202.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Jan 2007 16:29:47.0921 (UTC) FILETIME=[3689D810:01C73342] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/63 X-Sequence-Number: 24219 On Mon, 2007-01-08 at 09:41 -0600, Ben K. wrote: > > On Fri, 2007-01-05 at 12:59 -0600, Ben K. wrote: > >> 2. sql dump and PITR > >> Is it possible to use the PITR method with SQL dump? (pg_start_backup -> > >> sql dump -> pg_stop_backup) I guess not, but just want to make sure. > > > > No, because there is no reason or benefit. > > Thanks. I guess the PITR plays on a different ground. This is just a > superficial question, but would it be possible to separate sql and disk > operations? Eventually, it would be nice if we can have something like > these as example. (I don't have any experience with this product.) > > http://www.red-gate.com/products/SQL_Log_Rescue/ > > We sometimes have relatively minor but still painful problems (someone or > some scripts causes undesirable changes) and if we can go from the sql > dump (backup) and stop at a certain point, it would be really nice. It'd > also give us more granuality in controlling backup or test servers. There is a log analysis tool on pgfoundry that does something similar. You can already stop recovery at a certain point. So there's nothing to stop you doing a recovery on a development machine up to a certain point, then dumping the deleted data using pg_dump and re-loading it into the live server. Then erasing the dev recovered database. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com