Re: Protecting against unexpected zero-pages: proposal

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Protecting against unexpected zero-pages: proposal
Date: 2010-11-09 23:30:58
Message-ID: 20421.1289345458@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Though incidentally all of the other items you mentioned are generic
>> problems caused by with MVCC, not hint bits.

> Yes, but the hint bits prevent us from implementing workarounds.

If we got rid of hint bits, we'd need workarounds for the ensuing
massive performance loss. There is no reason whatsoever to imagine
that we'd come out ahead in the end.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-11-09 23:42:09 Re: Protecting against unexpected zero-pages: proposal
Previous Message Terry Laurenzo 2010-11-09 23:11:44 Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)