Add isolation tests for the combination of EPQ and triggers.
authorAndres Freund
Fri, 4 Oct 2019 20:56:04 +0000 (13:56 -0700)
committerAndres Freund
Fri, 4 Oct 2019 20:57:44 +0000 (13:57 -0700)
commit0cbc72ca72d4d7bdfecea6244bce6d5fb94e2e1a
tree51e105a6676169b6888fd8a0f48ee13fcde70b98
parent60e97d63e5d19098e11fa32431a20eea820e2ae9
Add isolation tests for the combination of EPQ and triggers.

As evidenced by bug #16036 this area is woefully under-tested. Add
fairly extensive tests for the combination.

Backpatch back to 9.6 - before that isolationtester was not capable
enough. While we don't backpatch tests all the time, future fixes to
trigger.c would potentially look different enough in 12+ from the
earlier branches that introducing bugs during backpatching is more
likely than normal. Also, it's just a crucial and undertested area of
the code.

Author: Andres Freund
Discussion: https://postgr.es/m/16036-28184c90d952fb7f@postgresql.org
Backpatch: 9.6-, the earliest these tests work
src/test/isolation/expected/eval-plan-qual-trigger.out [new file with mode: 0644]
src/test/isolation/isolation_schedule
src/test/isolation/specs/eval-plan-qual-trigger.spec [new file with mode: 0644]