Re: Proposal: Incremental Backup - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Proposal: Incremental Backup
Date
Msg-id CAA4eK1Kcu+FOwBrab-U-922XF2S6roYWF_+ERpQHnhF7m8ofaA@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Incremental Backup  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Proposal: Incremental Backup  (Michael Paquier <michael.paquier@gmail.com>)
Re: Proposal: Incremental Backup  (Bruce Momjian <bruce@momjian.us>)
Re: Proposal: Incremental Backup  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Jul 30, 2014 at 11:32 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> IMV, the way to eventually make this efficient is to have a background
> process that reads the WAL and figures out which data blocks have been
> modified, and tracks that someplace.

Nice idea, however I think to make this happen we need to ensure
that WAL doesn't get deleted/overwritten before this process reads
it (may be by using some existing param or mechanism) and 
wal_level has to be archive or more.

One more thing, what will happen for unlogged tables with such a 
mechanism?


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Production block comparison facility
Next
From: Amit Kapila
Date:
Subject: Re: Proposal: Incremental Backup