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

Re: Disabled features on Hot Standby

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Disabled features on Hot Standby
Date: 2012-01-14 05:44:06
Message-ID: CA+TgmoYbAbbB2szn9OUXVrCUS6EGRqedVDWaxN0s7yHO19vnJQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Jan 13, 2012 at 12:18 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Fri, Jan 13, 2012 at 5:08 PM, Robert Haas <robertmhaas(at)gmail(dot)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.

Interesting.  I hadn't considered that point.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Noah MischDate: 2012-01-14 06:10:14
Subject: Re: Disabled features on Hot Standby
Previous:From: Robert HaasDate: 2012-01-14 05:42:02
Subject: Re: Disabled features on Hot Standby

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