Re: Reduce maintenance burden of alternative output files with \if \quit

Hi, On 2018-11-07 08:21:09 +0100, Peter Eisentraut wrote: > On 05/11/2018 20:54, Andres Freund wrote: > > What mechanism are you referring to? Expected files and resultmap don't > > really fit that bill? > > We can add test files on the pg_regress command line based on makefile > conditionals. B

Re: Reduce maintenance burden of alternative output files with \if \quit

On 05/11/2018 20:54, Andres Freund wrote: > What mechanism are you referring to? Expected files and resultmap don't > really fit that bill? We can add test files on the pg_regress command line based on makefile conditionals. >> But some of those tests are used for testing that the unsupported >>

Re: Reduce maintenance burden of alternative output files with \if \quit

On 2018-11-05 15:08:33 +0100, Peter Eisentraut wrote: > On 03/11/2018 22:55, Andres Freund wrote: > > We have a few alterntive expected output files that are essentially full > > of errors, because a certain feature isn't supported. Those are somewhat > > painful to maintain. I wonder if it'd be a

Re: Reduce maintenance burden of alternative output files with \if \quit

On 03/11/2018 22:55, Andres Freund wrote: > We have a few alterntive expected output files that are essentially full > of errors, because a certain feature isn't supported. Those are somewhat > painful to maintain. I wonder if it'd be a good idea to reduce the > maintenance overhead for some of th

Reduce maintenance burden of alternative output files with \if \quit

Hi, We have a few alterntive expected output files that are essentially full of errors, because a certain feature isn't supported. Those are somewhat painful to maintain. I wonder if it'd be a good idea to reduce the maintenance overhead for some of them by putting something like SELECT NOT feat