Re: pg_regress writes into source tree

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_regress writes into source tree
Date: 2014-12-18 23:05:01
Message-ID: 54935D9D.7010608@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 12/18/2014 03:02 AM, Michael Paquier wrote:
> On Fri, Dec 12, 2014 at 10:45 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
>
>> Another thing in that patch was that I had to add the sql/ directory to
>> the source tree, but other than that .gitignore file it was empty.
>> Maybe pg_regress should create the sql/ directory in the build dir if it
>> doesn't exist. This is only a problem if a pg_regress suite only runs
>> stuff from input/, because otherwise the sql/ dir already exists in the
>> source.
> +1 for having pg_regress create the sql/ directory when it does not
> exist. Current behavior is annoying when modules having only tests in
> input/...

That seems like a separate issue. I think Peter should commit his patch
and backpatch it immediately, and we can deal with the missing sql
directory when someone sends in a patch.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-12-19 01:32:36 Re: Commitfest problems
Previous Message Jim Nasby 2014-12-18 23:00:08 Re: hash_create API changes (was Re: speedup tidbitmap patch: hash BlockNumber)