Re: Testing with concurrent sessions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Testing with concurrent sessions
Date
Msg-id 603c8f071001061715g649c7536uf093238f1e813b84@mail.gmail.com
Whole thread Raw
In response to Re: Testing with concurrent sessions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Testing with concurrent sessions
Re: Testing with concurrent sessions
List pgsql-hackers
On Wed, Jan 6, 2010 at 4:52 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> "David E. Wheeler" <david@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.)

Doing this without DBI is going to be ten times harder than doing it
with DBI.  Are we really sure that's not a viable option?

...Robert


pgsql-hackers by date:

Previous
From: Chuck McDevitt
Date:
Subject: Bug with PATHs having non-ASCII characters
Next
From: Takahiro Itagaki
Date:
Subject: Re: Bug with PATHs having non-ASCII characters