Re: Protecting against unexpected zero-pages: proposal

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Protecting against unexpected zero-pages: proposal
Date: 2010-11-09 20:25:25
Message-ID: AANLkTi=Yq1x0SNQiTd3-0STWbcf0FUfor_UeFK+1Urwv@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 9, 2010 at 8:12 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> The whole point of the hint bits is that it's in the same place as the data.
>
> Yes, but the hint bits are currently causing us trouble on several
> features or potential features:

Then we might have to get rid of hint bits. But they're hint bits for
a metadata file that already exists, creating another metadata file
doesn't solve anything.

Though incidentally all of the other items you mentioned are generic
problems caused by with MVCC, not hint bits.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jochem van Dieten 2010-11-09 21:12:15 Re: W3C Specs: Web SQL
Previous Message Peter Eisentraut 2010-11-09 20:18:29 multi-platform, multi-locale regression tests