Re: atomic pin/unpin causing errors - Mailing list pgsql-hackers

From Andres Freund
Subject Re: atomic pin/unpin causing errors
Date
Msg-id 20160503230524.2izoggmpjib76jgw@alap3.anarazel.de
Whole thread Raw
In response to atomic pin/unpin causing errors  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: atomic pin/unpin causing errors  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Re: atomic pin/unpin causing errors  (Teodor Sigaev <teodor@sigaev.ru>)
Re: atomic pin/unpin causing errors  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
Hi Jeff,

On 2016-04-29 10:38:55 -0700, Jeff Janes wrote:
> I've bisected the errors I was seeing, discussed in
> http://www.postgresql.org/message-id/CAMkU=1xQEhC0Ok4d+tkjFQ1nvUhO37PYRKhJP6Q8oxifMx7OwA@mail.gmail.com
> 
> It look like they first appear in:
> 
> commit 48354581a49c30f5757c203415aa8412d85b0f70
> Author: Andres Freund <andres@anarazel.de>
> Date:   Sun Apr 10 20:12:32 2016 -0700
> 
>     Allow Pin/UnpinBuffer to operate in a lockfree manner.
> 
> 
> I get the errors:
> 
> ERROR:  attempted to delete invisible tuple
> STATEMENT:  update foo set count=count+1,text_array=$1 where text_array @> $2
> 
> And also:
> 
> ERROR:  unexpected chunk number 1 (expected 2) for toast value
> 85223889 in pg_toast_16424
> STATEMENT:  update foo set count=count+1 where text_array @> $1

Hm. I appear to have trouble reproducing this issue (continuing to try)
on master as of 8826d8507.  Is there any chance you could package up a
data directory after the issue hit?


> (This was all run using Teodor's test-enabling patch
> gin_alone_cleanup-4.patch, so as not to change horses in midstream.
> Now that a version of that patch has been committed, I will try to
> repeat this in HEAD)

Any news on that front?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: what to revert
Next
From: Craig Ringer
Date:
Subject: Re: what to revert