Re: Re: Rethinking hint bits WAS: 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: Re: Rethinking hint bits WAS: Protecting against unexpected zero-pages: proposal
Date: 2010-11-15 18:24:48
Message-ID: 332.1289845488@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:
> No, I'm not. I'm pointing out that it doesn't unblock the other 4
> features/improvements I mentioned, *all* of which would be unblocked by
> not storing the hint bits in the table, whatever means we use to do so.
> You, for your part, are consistently ignoring these other issues.

I'm not ignoring them; I just choose to work on other issues, since
there is no viable proposal for fixing them. I don't intend to put
my time into dead ends.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2010-11-15 19:06:21 Re: Re: Rethinking hint bits WAS: Protecting against unexpected zero-pages: proposal
Previous Message Josh Berkus 2010-11-15 18:16:45 Re: Re: Rethinking hint bits WAS: Protecting against unexpected zero-pages: proposal