Re: Patch for fail-back without fresh backup

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for fail-back without fresh backup
Date: 2013-10-24 10:52:12
Message-ID: 5268FBDC.10106@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24.10.2013 13:02, Pavan Deolasee wrote:
> Another difference AFAICS is that checksum feature needs the block to be
> backed up only after the first time a hint bit is updated after checkpoint.
> But for something like pg_rewind to work, we will need to WAL log every
> hint bit update on a page. So we would want to keep it as short as possible.

To fix that, pg_rewind could always start the rewinding process from the
last checkpoint before the point that the histories diverge, instead of
the exact point of divergence. That would make the rewinding more
expensive as it needs to read through a lot more WAL, but I think it
would still be OK.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-10-24 11:09:18 Re: Ident context leak during reloading of conf files when no ident information is present in the file
Previous Message Thom Brown 2013-10-24 10:41:11 Re: 9.4 regression