Re: SetBufferCommitInfoNeedsSave and race conditions

"Simon Riggs" <simon@2ndquadrant.com> writes:
> On Thu, 2007-06-28 at 20:23 -0400, Tom Lane wrote:
>> The methodology I suggested earlier (involving tracking LSN only at the
>> level of pg_clog pages) isn't going to make that work, unless you
>> somehow force the XID counter forward to the next page boundary.

> If you completely flush WAL after the AccessExclusiveLock has been taken
> by VF, then you are guaranteed to have flushed all asynchronous commits
> that touch the table.

I don't believe this is correct (see system catalogs) and in any case
it's far too fragile for my taste.  I think it'd be a lot better to just
stop referencing the hint bits directly in VACUUM FULL.
        regards, tom lane