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

Re: Testing with concurrent sessions

From: Markus Wanner <markus(at)bluegap(dot)ch>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org, Michael Tan <mtanhl(at)gmail(dot)com>, david(at)kineticode(dot)com
Subject: Re: Testing with concurrent sessions
Date: 2010-01-14 20:08:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Markus Wanner wrote:
> Sorry, if that didn't get clear. I'm trying to put together something I 
> can release real soon now (tm). I'll keep you informed.

Okay, here we go: dtester version 0.0.

This emerged out of Postgres-R, where I don't just need to test multiple 
client connections, but multiple postmasters interacting with each 
other. None the less, it may be suitable for other needs as well, 
especially testing with concurrent sessions.

I've decided to release this as a separate project named dtester, as 
proposed by Michael Tan (thanks for your inspiration).

It's certainly missing lots of things, mainly documentation. However, 
I've attached a patch which integrates nicely into the Postgres 
Makefiles, so you just need to say: make dcheck.

That very same patch includes a test case with three concurrent 
transactions with circular dependencies, where the current SERIALIZABLE 
isolation level fails to provide serializability.

Installing dtester itself is as simple as 'python install' in 
the extracted archive's directory.

Go try it, read the code and simply ask, if you get stuck. I'll try to 
come up with some more documentation and such...


Markus Wanner

Attachment: dtester-0.0.tar.bz2
Description: application/x-bzip (10.1 KB)
Attachment: dtester-0.0-postgres-integration-example.diff
Description: text/x-patch (24.7 KB)

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-01-14 20:13:46
Subject: Re: Streaming replication, retrying from archive
Previous:From: Tom LaneDate: 2010-01-14 19:56:20
Subject: Re: EXPLAIN, utility statement parameters, and recent plpgsql changes

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