Greg Stark <gsst...@mit.edu> writes:
> On Sun, Aug 23, 2009 at 7:34 PM, Tom Lane<t...@sss.pgh.pa.us> wrote:
>> Urgh. I bet that's where the problem is then. Some path is failing
>> to clear that bit, or maybe there's a race condition that allows it
>> to become set incorrectly (ie right after somebody else adds a tuple).
> Well it only gets set in vacuum when we have the vacuum cleanout lock
> so I can't see it getting set incorrectly unless there's a simple
> logic error in vacuum. I just scanned it and it looks right to me.
heap_update is broken. Details left as an exercise for the reader
(hint: Heikki has blatantly ignored the WAL-logging rules in transam/README)
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
