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

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Andres Freund <andres(at)anarazel(dot)de>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: HeapTupleSatisfiesToast() busted? (was atomic pin/unpin causing errors)
Date: 2016-05-11 14:06:05
Message-ID: 57333C4D.2090008@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> 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.

--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-05-11 14:12:26 Re: asynchronous and vectorized execution
Previous Message Robert Haas 2016-05-11 14:00:01 Re: asynchronous and vectorized execution