Re: BUG #14150: Attempted to delete invisible tuple

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
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 01:45:38
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

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.

regards, tom lane

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message 甄明洋 2016-08-18 09:57:48 Re:Re: Re:Re: Re: [BUGS] Return value error of‘to_timestamp’
Previous Message Michael Paquier 2016-08-18 00:25:54 Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file