Re: Testing with concurrent sessions

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <robertmhaas(at)gmail(dot)com>,<tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <andrew(at)dunslane(dot)net>,<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:43:24
Message-ID: 4B44F5EC020000250002DE4B@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> We have not yet fully accepted the notion that you must have Perl
> to build (and, in fact, I am right now trying to verify that you
> don't). I don't think that requiring Perl to test is going to fly.

Well, if that's the consensus, I have to choose between trying to
implement multi-session psql and using testing which can't carry over
to long-term regular use. Are we anywhere close to an agreement on
what the multi-session psql implementation would look like? (If not
I can put something forward.)

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2010-01-07 02:49:14 Re: Bug with PATHs having non-ASCII characters
Previous Message Kevin Grittner 2010-01-07 02:31:20 Re: Testing with concurrent sessions