Re: Testing with concurrent sessions

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Markus Wanner" <markus(at)bluegap(dot)ch>
Cc: "Michael Tan" <mtanhl(at)gmail(dot)com>,<david(at)kineticode(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Testing with concurrent sessions
Date: 2010-01-14 20:23:01
Message-ID: 4B4F28C5020000250002E4C6@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Markus Wanner <markus(at)bluegap(dot)ch> wrote:

> Okay, here we go: dtester version 0.0.

C'mon, you could have tried to inspire a *bit* more confidence by
calling it version 0.1 or something! ;-)

> 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 sounds very cool.

> 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.

Fantastic! I'll expand that a bit....

> Installing dtester itself is as simple as 'python setup.py
> 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...

I'm reading through it all now. Expect feedback soon!

And THANK YOU VERY MUCH!

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-14 20:42:37 Re: EXPLAIN, utility statement parameters, and recent plpgsql changes
Previous Message Dimitri Fontaine 2010-01-14 20:17:57 Re: EXPLAIN, utility statement parameters, and recent plpgsql changes