Skip site navigation (1) Skip section navigation (2)

pgsql: Add support for blocked commands in isolationtester

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add support for blocked commands in isolationtester
Date: 2011-07-12 21:28:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
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

Author: Noah Misch



Modified Files
src/test/isolation/README                     |   13 ++
src/test/isolation/expected/fk-contention.out |   17 ++
src/test/isolation/expected/fk-deadlock.out   |   67 ++++++++
src/test/isolation/expected/fk-deadlock2.out  |  107 ++++++++++++
src/test/isolation/isolation_schedule         |    3 +
src/test/isolation/isolationtester.c          |  215 +++++++++++++++++++++----
src/test/isolation/specs/fk-contention.spec   |   19 +++
src/test/isolation/specs/fk-deadlock.spec     |   54 ++++++
src/test/isolation/specs/fk-deadlock2.spec    |   59 +++++++
9 files changed, 524 insertions(+), 30 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2011-07-12 22:25:14
Subject: pgsql: Avoid listing ungrouped Vars in the targetlist ofAgg-underneath
Previous:From: Joshua D. DrakeDate: 2011-07-12 16:30:02
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group