Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-02-20 Thread Christoph Berg
Re: Peter Eisentraut 2019-02-20 <40c5c12f-adad-fc86-7d43-ff7c53535...@2ndquadrant.com> > > By the same argument, it should always print which variant file was > > used so determining which _N.out files are still in use is possible. > > I would rather not overload the test output even more. A tes

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-02-20 Thread Peter Eisentraut
On 2019-02-15 16:05, Christoph Berg wrote: > Re: Andrew Gierth 2019-02-15 <874l95m8w7@news-spur.riddles.org.uk> >> Also while we're tweaking regression test output, would it be possible >> to have some indicator of whether a test passed because a variant file >> in the resultmap was ignored in

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-02-20 Thread Peter Eisentraut
On 2019-01-03 12:16, Peter Eisentraut wrote: > On 03/01/2019 10:39, Christoph Berg wrote: >> It will especially say which _alternate.out file was used, which seems >> like a big win. So +1. > > It already shows that in the existing diff output header. > > Although if you have a really long absolu

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-02-15 Thread Christoph Berg
Re: Andrew Gierth 2019-02-15 <874l95m8w7@news-spur.riddles.org.uk> > Also while we're tweaking regression test output, would it be possible > to have some indicator of whether a test passed because a variant file > in the resultmap was ignored in favor of the standard result? > > The current s

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-02-15 Thread Andrew Gierth
> "Peter" == Peter Eisentraut writes: Peter> (This might be one of those rare times where one hopes for a Peter> buildfarm failure for verification. :-) ) Also while we're tweaking regression test output, would it be possible to have some indicator of whether a test passed because a varian

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-02-15 Thread Peter Eisentraut
On 2019-01-03 11:20, Daniel Gustafsson wrote: >> On 3 Jan 2019, at 10:39, Christoph Berg wrote: >> >> Re: Peter Eisentraut 2019-01-02 >> <70440c81-37bb-76dd-e48b-b5a9550d5...@2ndquadrant.com> > >>> While we're considering the pg_regress output, what do you think about >>> replacing the ==...

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-01-03 Thread Peter Eisentraut
On 03/01/2019 10:39, Christoph Berg wrote: > It will especially say which _alternate.out file was used, which seems > like a big win. So +1. It already shows that in the existing diff output header. Although if you have a really long absolute path, it might be hard to find it. So perhaps the att

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-01-03 Thread Peter Eisentraut
On 02/01/2019 21:44, Tom Lane wrote: > Peter Eisentraut writes: >> 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,

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-01-03 Thread Daniel Gustafsson
> On 3 Jan 2019, at 10:39, Christoph Berg wrote: > > Re: Peter Eisentraut 2019-01-02 > <70440c81-37bb-76dd-e48b-b5a9550d5...@2ndquadrant.com> >> While we're considering the pg_regress output, what do you think about >> replacing the ==... separator with a standard diff separator like >> "di

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-01-03 Thread Christoph Berg
Re: Peter Eisentraut 2019-01-02 <70440c81-37bb-76dd-e48b-b5a9550d5...@2ndquadrant.com> > Committed. \o/ > 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

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-01-02 Thread Tom Lane
Peter Eisentraut writes: > 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 th

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2019-01-02 Thread Peter Eisentraut
On 22/11/2018 14:10, Christoph Berg wrote: > It's nice that PG_REGRESS_DIFF_OPTS exists, but the diffs are often > coming from automated build logs where setting the variable after the > fact doesn't help. > > Please consider the attached patch, extension packagers will thank > you. Committed. W

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2018-11-25 Thread David Fetter
On Thu, Nov 22, 2018 at 02:10:59PM +0100, Christoph Berg wrote: > Re: Noah Misch 2017-04-07 <20170407021431.gb2658...@tornado.leadboat.com> > > > > I personally, and I know of a bunch of other regular contributors, find > > > > context diffs very hard to read. Besides general dislike, for things >

Re: [HACKERS] Time to change pg_regress diffs to unified by default?

2018-11-22 Thread Christoph Berg
Re: Noah Misch 2017-04-07 <20170407021431.gb2658...@tornado.leadboat.com> > > > I personally, and I know of a bunch of other regular contributors, find > > > context diffs very hard to read. Besides general dislike, for things > > > like regression test output context diffs are just not well suite