]> granicus.if.org Git - postgresql/commit
Add support for blocked commands in isolationtester
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 12 Jul 2011 20:35:09 +0000 (16:35 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 12 Jul 2011 21:24:17 +0000 (17:24 -0400)
commit846af54dd5a77dc02feeb5e34283608012cfb217
tree116e0a640b29bc2bda7700cdd22ff5659a7fd0d4
parentfd6913a18955b0f89ca994b5036c103bcea23f28
Add support for blocked commands in isolationtester

This enables us to test that blocking commands (such as foreign keys
checks that conflict with some other lock) act as intended.  The set of
tests that this adds is pretty minimal, but can easily be extended by
adding new specs.

The intention is that this will serve as a basis for ensuring that
further tweaks of locking implementation preserve (or improve) existing
behavior.

Author: Noah Misch
src/test/isolation/README
src/test/isolation/expected/fk-contention.out [new file with mode: 0644]
src/test/isolation/expected/fk-deadlock.out [new file with mode: 0644]
src/test/isolation/expected/fk-deadlock2.out [new file with mode: 0644]
src/test/isolation/isolation_schedule
src/test/isolation/isolationtester.c
src/test/isolation/specs/fk-contention.spec [new file with mode: 0644]
src/test/isolation/specs/fk-deadlock.spec [new file with mode: 0644]
src/test/isolation/specs/fk-deadlock2.spec [new file with mode: 0644]