Re: [HACKERS] Time to change pg_regress diffs to unified by default? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Time to change pg_regress diffs to unified by default?
Date
Msg-id 5b72cf02-61e1-0219-cc91-c6b4e4144c8b@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Time to change pg_regress diffs to unified by default?  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: [HACKERS] Time to change pg_regress diffs to unified by default?
List pgsql-hackers
On 2019-01-03 11:20, Daniel Gustafsson wrote:
>> On 3 Jan 2019, at 10:39, Christoph Berg <myon@debian.org> wrote:
>>
>> Re: Peter Eisentraut 2019-01-02 <70440c81-37bb-76dd-e48b-b5a9550d5613@2ndquadrant.com>
> 
>>> While we're considering the pg_regress output, what do you think about
>>> replacing the ======... separator with a standard diff separator like
>>> "diff %s %s %s\n".  This would make the file behave more like a proper
>>> diff file, for use with other tools.  And it shows the diff options
>>> used, for clarity.  See attached patch.
>>
>> It will especially say which _alternate.out file was used, which seems
>> like a big win. So +1.
> 
> That has bitten more times than I’d like to admit, so definately +1 on being
> explicit about that.

committed

(This might be one of those rare times where one hopes for a buildfarm
failure for verification. :-) )

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Reporting script runtimes in pg_regress
Next
From: Darafei Praliaskouski
Date:
Subject: Re: [PATCH][PROPOSAL] Add enum releation option type