Re: BUG #14150: Attempted to delete invisible tuple

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Oskari Saarenmaa <os(at)aiven(dot)io>, Peter Geoghegan <pg(at)heroku(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Tripp <peter(at)chartio(dot)com>, Virendra Negi <virendra(at)idyllic-software(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14150: Attempted to delete invisible tuple
Date: 2016-08-18 19:46:39
Message-ID: 20160818194639.e3izk4gfm2srmumm@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2016-08-17 21:45:38 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-08-18 20:38:39 Re: BUG #14150: Attempted to delete invisible tuple
Previous Message rotten 2016-08-18 19:06:23 BUG #14290: materialized view refresh doesn't use temp_tablespace