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

From Andres Freund
Subject Re: atomic pin/unpin causing errors
Date
Msg-id 20160505185945.iflpbpyiltzhnj5m@alap3.anarazel.de
Whole thread Raw
In response to Re: atomic pin/unpin causing errors  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: atomic pin/unpin causing errors  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
On 2016-05-04 18:12:45 +0300, Teodor Sigaev wrote:
> > > 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?
> 
> I've got
> ERROR:  unexpected chunk number 0 (expected 1) for toast value 10192986 in
> pg_toast_16424
> 
> The test required 10 hours to run on my notebook. postgresql was compiled
> with -O0 --enable-debug --enable-cassert.

Hm. And you're not seeing the asserts I reported in
http://archives.postgresql.org/message-id/20160505185246.2i7qftadwhzewykj%40alap3.anarazel.de
?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: atomic pin/unpin causing errors
Next
From: Tom Lane
Date:
Subject: Poorly-thought-out handling of double variables in pgbench