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 03:00:30
Message-ID: 4B44F9EE020000250002DE5C@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:

> I'm not exactly sure what Kevin's goal is here.

I think it would be insane to try to do something like serializable
isolation mode without having regression tests. I would want more
tests than could reasonably go into the 'make check' suite to support
development, but it would be very good to have some go in there.

> For basic regression tests, yeah, we'd probably like to keep that
> Perl-free.

OK. Is parallel psql the only reasonable option?

> For more complex testing, I think using Perl makes sense. Or to put
> the shoe on the other foot, if we DON'T allow the use of Perl for
> more complex testing, then we're probably not going to have any
> more complex tests.

Do you envision some test suite committed to CVS beyond the 'make
check' tests, for "on demand" testing at a more rigorous level?
Am I missing something that's already there?

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-01-07 03:05:24 Re: Testing with concurrent sessions
Previous Message Robert Haas 2010-01-07 03:00:08 Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).