isolationtester and invalid permutations

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Alvaro Herrera <alvherre@alvh.no-ip.org>

To: Pg Hackers <pgsql-hackers@postgresql.org>

Cc: Noah Misch <noah@leadboat.com>, Kevin Grittner <kevin.grittner@wicourts.gov>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

Date: 2011-10-26T01:13:24Z

Lists: pgsql-hackers

Attachments

isotester-allow-invalid-perms.patch (application/octet-stream) patch

Instead of simply aborting a spec that specifies running commands on
blocked sessions (what we call an invalid permutation), it seems more
useful to report the problem, cleanup the sessions, and continue with
the next permutation.

This, in conjunction with the dry-run patch I submitted earlier, makes
it easier to determine a working spec: dry-run the spec; copy the
so-generated permutation lines into the spec; run the spec normally,
which reports the invalid permutations; comment out the invalid
permutations from the spec; done.

The attached patch, again from Alexander Shulgin (with some tweaks from
me) does that.

Comments?

-- 
Álvaro Herrera <alvherre@alvh.no-ip.org>