From: | Andrew Piskorski <atp(at)piskorski(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matt Miller <mattm(at)epx(dot)com> |
Subject: | Re: Testing of MVCC |
Date: | 2005-08-16 11:45:35 |
Message-ID: | 20050816114535.GB48544@tehun.pair.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Mon, Aug 15, 2005 at 06:01:20PM -0400, Tom Lane wrote:
> What we really need is a test program that can issue a command on one
> connection (perhaps waiting for it to finish, perhaps not) and then
> issue other commands on other connections, all according to a script.
Well, using Tcl with its Tcl Threads Extension should certainly let
you easily control multiple concurrent PostgreSQL connections. (The
Thread Extension's APIs are particularly nice for multi-threaded
programming.) Its docs are here:
http://cvs.sourceforge.net/viewcvs.py/tcl/thread/doc/html/
> I am unsure that the existing pg_regress infrastructure is the right
> place to start from. Perhaps we should look at Expect or something
> similar.
I don't have any clear idea of what sort of tests you want to run
"according to a script" though, so I'm not sure whether the Tcl
Threads Extension, or Expect, or some other tool would best meet your
needs.
--
Andrew Piskorski <atp(at)piskorski(dot)com>
http://www.piskorski.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2005-08-16 12:04:15 | Re: regarding isolation amongst threads |
Previous Message | Surabhi Ahuja | 2005-08-16 10:36:57 | regarding isolation amongst threads |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2005-08-16 12:08:07 | Re: pl/Ruby, deprecating plPython and Core |
Previous Message | Jake Stride | 2005-08-16 08:33:05 | Cascades Failing |