Re: Add more regression tests for dbcommands

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robins Tharakan <tharakan(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add more regression tests for dbcommands
Date: 2013-06-27 22:55:02
Message-ID: 1372373702.25247.YahooMailNeo@web162901.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:

> On 6/27/13 10:20 AM, Robert Haas wrote:
>> So I'd like to endorse Josh's idea: subject to appropriate review,
>> let's add these test cases.  Then, if it really turns out to be too
>> burdensome, we can take them out, or figure out a sensible way to
>> split the suite.  Pushing all of Robins work into a secondary suite,
>> or throwing it out altogether, both seem to me to be things which will
>> not be to the long-term benefit of the project.
>
> I agree.  If it gets too big, let's deal with it then.  But let's not
> make things more complicated because they *might* get too big later.

+1

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2013-06-27 23:10:32 Re: MD5 aggregate
Previous Message Noah Misch 2013-06-27 22:35:20 Re: proposal: enable new error fields in plpgsql (9.4)