Re: HeapTupleSatisfiesToast() busted? (was atomic pin/unpin causing errors)

On May 11, 2016 7:06:05 AM PDT, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
>>> Allow Pin/UnpinBuffer to operate in a lockfree manner.
>>> I get the errors:
>>>
>>> ERROR: attempted to delete invisible tuple
>>> ERROR: unexpected chunk number 1 (expected 2) for toast value
>
>Just reminder, you investigate "unexpected chunk number" problem, but,
>seems, we
>have another bug (first ERROR: attempted to delete invisible tuple).
>IMHO, it's
>a separate bug, not related to oid. Unfortunately, I've never seen such
>error on
>my notebook.

Same issue. If the dead tuple is noticed by heap_delete (when it should have deleted the live version elsewhere) you get the invisible role error. The unexpected chunk bit only triggers with hint bit sets differently across chunks.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.