Horton

Re: BUG #16036: Segmentation fault while doing an update

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Geoghegan <pg@bowt.ie>, pgsql-bugs@lists.postgresql.org
Date: 2019-10-05T16:26:59Z
Lists: pgsql-bugs 
Hi,

On 2019-10-05 11:30:39 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > I've now disabled that portion of the test.
> 
> There's still a large fraction of the buildfarm that's unhappy :-(

I pushed a second patch disabling two more permutations, I've not seen
any related failures since.  It's frustrating that we at the moment seem
to not have deterministic behaviour with two sessions waiting for a
tuple lock at the moment. Doesn't look like that's new though.

It seems to me that most of the XactLockTableWait() users ought to
follow the pattern outlined at the top of README.tuplock, but
don't.

Greetings,

Andres Freund

Commits

  1. Disable one more set of tests from c8841199509.

  2. Disable one set of tests from c8841199509.

  3. Add isolation tests for the combination of EPQ and triggers.

  4. Fix crash caused by EPQ happening with a before update trigger present.

  5. Modify the isolation tester so that multiple sessions can wait.