pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Ben K. <bkim@coe.tamu.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: PITR recovery
Date: Mon, 08 Jan 2007 16:28:45 +0000
Message-ID: <1168273726.3951.202.camel@silverbirch.site> (raw)
In-Reply-To: <Pine.GSO.4.64.0701080915170.1259@coe.tamu.edu>
References: <Pine.GSO.4.64.0701051218340.1164@coe.tamu.edu>
	<1168097862.3655.249.camel@silverbirch.site>
	<Pine.GSO.4.64.0701080915170.1259@coe.tamu.edu>

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





view thread (10+ messages)  latest in thread

Message-ID: <1168273726.3951.202.camel@silverbirch.site>
Permalink:  ../1168273726.3951.202.camel@silverbirch.site/
Also on:    postgresql.org/message-id/1168273726.3951.202.camel@silverbirch.site

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: simon@2ndquadrant.com, bkim@coe.tamu.edu
  Subject: Re: PITR recovery
  In-Reply-To: <1168273726.3951.202.camel@silverbirch.site>
  References: <Pine.GSO.4.64.0701051218340.1164@coe.tamu.edu> <1168097862.3655.249.camel@silverbirch.site> <Pine.GSO.4.64.0701080915170.1259@coe.tamu.edu> <1168273726.3951.202.camel@silverbirch.site>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox