Re: [HACKERS] Time to change pg_regress diffs to unified by default?
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Daniel Gustafsson <daniel@yesql.se>, Christoph Berg <myon@debian.org>
Cc: Noah Misch <noah@leadboat.com>, Tom Lane <tgl@sss.pgh.pa.us>,
Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Date: 2019-02-15T14:16:00Z
Lists: 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
Commits
-
pg_regress: Don't use absolute paths for the diff
- 1995552deb54 12.0 landed
-
Use standard diff separator for regression.diffs
- 8f27a14b1bd3 12.0 landed