From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Matt Miller <mattm(at)epx(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Testing of MVCC |
Date: | 2005-08-16 00:55:53 |
Message-ID: | 19637.1124153753@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Or else a harness that operates at the library/connection level rather
> than trying to control a tty app.
Right. What is sort of in the back of my mind is a C program that can
open more than one connection, and it reads a script that tells it
"fire this command out on this connection". The question at hand is
whether we can avoid re-inventing the wheel.
> Expect is very cool, but it would impose an extra dependency on tcl that
> we don't now have for building and testing,
True. I was pointing to it more as an example of the sorts of tools
people have built for this type of problem.
I'm pretty sure there are re-implementations of Expect out there that
don't use Tcl; would you be happier with, say, a perl-based tool?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-08-16 01:25:20 | Re: How to write jobs in postgresql |
Previous Message | Bill Moseley | 2005-08-16 00:30:08 | Re: Sorting by related tables |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-08-16 01:33:54 | Re: Testing of MVCC |
Previous Message | Andrew Dunstan | 2005-08-15 23:31:19 | Re: Testing of MVCC |