Re: Testing with concurrent sessions

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <andrew(at)dunslane(dot)net>,<robertmhaas(at)gmail(dot)com>
Cc: <peter_e(at)gmx(dot)net>,<david(at)kineticode(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Testing with concurrent sessions
Date: 2010-01-07 02:31:20
Message-ID: 4B44F318020000250002DE3D@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
> Robert Haas wrote:

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

> In the buildfarm? Yes, I think so. The philosophy of the buildfarm
> is that it should do what you would do yourself by hand.
>
> And adding DBI as a requirement for running a buildfarm member
> would be a significant extra barrier to entry, ISTM. (I am very
> fond of DBI, and use it frequently, BTW)
>
> I'm persuadable on most things, but this one would take a bit of
> doing.

As far as I've been able to determine so far, to call psql in a
relatively portable way would require something like this:

http://perldoc.perl.org/perlfork.html

Is that really better than DBI?

Don't we need some way to routinely test multi-session issues?

Other ideas?

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-01-07 02:43:24 Re: Testing with concurrent sessions
Previous Message Tom Lane 2010-01-07 02:26:29 Re: Testing with concurrent sessions