From: "Kevin Grittner" on 5 Jan 2010 11:48 Markus Wanner <markus(a)bluegap.ch> wrote: > Kevin Grittner wrote: >> It's very soon going to be critical that I be able to test >> particular interleavings of statements in particular concurrent >> transaction sets to be able to make meaningful progress on the >> serializable transaction work. > > I've something in place for Postgres-R, as I also need to test > concurrent transactions there. It's based on python/twisted and is > able to start multiple Postgres instances (as required for testing > replication) and query them concurrently (as you seem to need as > well). It uses an asynchronous event loop (from twisted) and > basically controls processes, issues queries and checks results > and ordering constraints (e.g. transaction X must commit and > return a result before transaction Y). Where would I find this (and any related documentation)? -Kevin -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Markus Wanner on 5 Jan 2010 14:06 Hi, Kevin Grittner wrote: > Where would I find this (and any related documentation)? 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. Regards Markus Wanner -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Kevin Grittner" on 6 Jan 2010 16:52 "David E. Wheeler" <david(a)kineticode.com> wrote: > Last I heard, Andrew was willing to require Test::More for > testing, so that a Perl script could handle multiple psql > connections (perhaps forked) and output test results based on > them. But he wasn't as interested in requiring DBI and DBD::Pg, > neither of which are in the Perl core and are more of a PITA to > install (not huge, but the barrier might as well stay low). OK, I've gotten familiar with Perl as a programming language and tinkered with Test::More. What's not clear to me yet is what would be considered good technique for launching several psql sessions from that environment, interleaving commands to each of them, and checking results from each of them as the test plan progresses. Any code snippets or URLs to help me understand that are welcome. (It seems clear enough with DBI, but I'm trying to avoid that per the above.) -Kevin -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Peter Eisentraut on 6 Jan 2010 17:08 On ons, 2010-01-06 at 15:52 -0600, Kevin Grittner wrote: > "David E. Wheeler" <david(a)kineticode.com> wrote: > > > Last I heard, Andrew was willing to require Test::More for > > testing, so that a Perl script could handle multiple psql > > connections (perhaps forked) and output test results based on > > them. But he wasn't as interested in requiring DBI and DBD::Pg, > > neither of which are in the Perl core and are more of a PITA to > > install (not huge, but the barrier might as well stay low). > > OK, I've gotten familiar with Perl as a programming language and > tinkered with Test::More. What's not clear to me yet is what would > be considered good technique for launching several psql sessions > from that environment, interleaving commands to each of them, and > checking results from each of them as the test plan progresses. Any > code snippets or URLs to help me understand that are welcome. (It > seems clear enough with DBI, but I'm trying to avoid that per the > above.) Then I don't see much of a point in using Perl. You might as well fire up a few psqls from a shell script. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "David E. Wheeler" on 6 Jan 2010 17:09
On Jan 6, 2010, at 1:52 PM, Kevin Grittner wrote: >> Last I heard, Andrew was willing to require Test::More for >> testing, so that a Perl script could handle multiple psql >> connections (perhaps forked) and output test results based on >> them. But he wasn't as interested in requiring DBI and DBD::Pg, >> neither of which are in the Perl core and are more of a PITA to >> install (not huge, but the barrier might as well stay low). > > OK, I've gotten familiar with Perl as a programming language and > tinkered with Test::More. What's not clear to me yet is what would > be considered good technique for launching several psql sessions > from that environment, interleaving commands to each of them, and > checking results from each of them as the test plan progresses. Any > code snippets or URLs to help me understand that are welcome. (It > seems clear enough with DBI, but I'm trying to avoid that per the > above.) Probably the simplest way is to use the core IPC::Open3 module: http://search.cpan.org/perldoc?IPC::Open3 IPC::Run might be easier to use if it's available, but it's not in Perl core, so YMMV. Really it's up to andrew what modules he requires test servers to have. Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |