From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gokulakannan Somasundaram <gokul007(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: An idle thought |
Date: | 2010-03-18 21:11:45 |
Message-ID: | 34d269d41003181411p1a0812cbp4cdb93cdccc5b752@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 18, 2010 at 15:07, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Thu, 2010-03-18 at 16:50 -0400, Tom Lane wrote:
>> The VM is (a) not compressed and (b) not correctness-critical.
>> Wrong bit values don't do any serious damage.
>
> The VM cause wrong results if a bit is set that's not supposed to be --
> right? Am I missing something? How does a seq scan skip visibility
> checks and still produce right results, if it doesn't rely on the bit?
Isn't it only really used for VACUUM at this point?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-03-18 21:17:15 | Re: An idle thought |
Previous Message | Jeff Davis | 2010-03-18 21:07:00 | Re: An idle thought |