Re: [HACKERS] PROVE_FLAGS - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [HACKERS] PROVE_FLAGS
Date
Msg-id ce17acd8-c671-3f41-ef69-ee73f0c2c202@2ndQuadrant.com
Whole thread Raw
In response to Re: [HACKERS] PROVE_FLAGS  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [HACKERS] PROVE_FLAGS  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers

On 05/04/2017 12:50 AM, Stephen Frost wrote:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>>> Can someone please explain to me why we have this in Makefile.global.in?
>>> (from commit e9c81b60 )
>>>     PROVE_FLAGS =
>> Before that commit it was like
>>
>>     PROVE_FLAGS = --verbose
> right.
>
>> which had some value.  I agree that now we'd be better off to not
>> set it at all, especially since the convention now appears to be that
>> automatically-supplied prove options should be set in PG_PROVE_FLAGS.
> Good point.
>
>> I'd suggest that the comment just above be replaced by something like
>>
>> # User-supplied prove flags can be provided in PROVE_FLAGS.
> Works for me.
>


Does anyone object to me backpatching this? It seems to me kinda crazy
to have --verbose hardcoded on the back branches and not on the dev branch.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Rahila Syed
Date:
Subject: Re: [HACKERS] Adding support for Default partition in partitioning
Next
From: tushar
Date:
Subject: [HACKERS] Getting error at the time of dropping subscription and few moreissues