Re: Disabled features on Hot Standby - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Disabled features on Hot Standby
Date
Msg-id CA+U5nMLk+7vzGfAieR1XiHhbc1eqDwOTPsZLg_0pSY+7Z77iiw@mail.gmail.com
Whole thread Raw
In response to Re: Disabled features on Hot Standby  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Disabled features on Hot Standby  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Jan 13, 2012 at 5:08 PM, Robert Haas <robertmhaas@gmail.com> wrote:

> Also, what happens if an all-visible bit gets set on the standby
> through some other mechanism - e.g. restored from an FPI or
> XLOG_HEAP_NEWPAGE?  I'm not sure whether we ever do an FPI of the
> visibility map page itself, but we certainly do it for the heap pages.
>  So it might be that this infrastructure would (somewhat bizarrely)
> trust the visibility map bits but not the PD_ALL_VISIBLE bits.  I'm
> hoping Heikki or Tom will comment on this thread, because I think
> there are a bunch of subtle issues here and that we could easily screw
> it up by trying to plow through the problem too hastily.

An FPI can't change the all visible flag. If it did, it would imply
that we'd skipped generation or replay of an XLOG_HEAP2_VISIBLE
record, or that we're doing crash recovery/inital startup and HS is
not yet enabled.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: checkpoint writeback via sync_file_range
Next
From: Tom Lane
Date:
Subject: Re: Remembering bug #6123