Re: BUG #14150: Attempted to delete invisible tuple - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #14150: Attempted to delete invisible tuple
Date
Msg-id 20160818194639.e3izk4gfm2srmumm@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #14150: Attempted to delete invisible tuple  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #14150: Attempted to delete invisible tuple
List pgsql-bugs
On 2016-08-17 21:45:38 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > I pushed a lightly editorialized version of this. The changes primarily
> > were around the regression test:
>
> > 1) The test originally hung for me every few executions - there's no
> >    guarantee whether s2 or s3 gets to run first. Removing the
> >    transaction from the inserting xacts should do the trick.
>
> guaibasaurus thinks this test is still underdetermined.

The easiest solution here seems to be another expected file - playing
around a few minutes, I couldn't see an easier solution. Better ideas?

Regards,

Andres

pgsql-bugs by date:

Previous
From: rotten@windfish.net
Date:
Subject: BUG #14290: materialized view refresh doesn't use temp_tablespace
Next
From: Tom Lane
Date:
Subject: Re: BUG #14150: Attempted to delete invisible tuple