Skip site navigation (1) Skip section navigation (2)


From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: FPI
Date: 2011-01-31 15:01:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Jan 28, 2011 at 3:39 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> What happens if we (a) keep the current rule after reaching
> consistency and (b) apply any such updates *unconditionally* - that
> is, without reference to the LSN - prior to reaching consistency?
> Under that rule, if we encounter an FPI before reaching consistency,
> we're OK.  So let's suppose we don't.  No matter how many times we
> replay any initial prefix of any such updates between the redo pointer
> and the point at which we reach consistency, the state of the page
> when we finally reach consistency will be identical.  But we could get
> hosed if replay progressed *past* the minimum recovery point and then
> started over at the previous redo pointer.  If we forced an immediate
> restartpoint on reaching consistency, that seems like it might prevent
> that scenario.

Actually, I'm wrong, and this doesn't work at all.  At the time of the
crash, there could already be pages on disk with LSNs greater than the
minimum recovery point.  Duh.

It was such a good idea in my head...

Robert Haas
The Enterprise PostgreSQL Company

In response to

  • Re: FPI at 2011-01-28 20:39:33 from Robert Haas


  • Re: FPI at 2011-02-01 02:28:43 from Robert Haas

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2011-01-31 15:02:39
Subject: Re: Snapshots no longer build
Previous:From: Heikki LinnakangasDate: 2011-01-31 14:52:27
Subject: Re: Spread checkpoint sync

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group