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

isolationtester and invalid permutations

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Subject: isolationtester and invalid permutations
Date: 2011-10-26 01:13:24
Message-ID: 1319591143-sup-7036@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
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(at)alvh(dot)no-ip(dot)org>

Attachment: isotester-allow-invalid-perms.patch
Description: application/octet-stream (3.6 KB)

Responses

pgsql-hackers by date

Next:From: Chris RedekopDate: 2011-10-26 01:24:50
Subject: Re: Hot Backup with rsync fails at pg_clog if under load
Previous:From: Tom LaneDate: 2011-10-26 01:06:10
Subject: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified

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