On Tue, Sep 12, 2017 at 9:19 PM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > On 9/11/17 18:21, Michael Paquier wrote: >> On Tue, Sep 12, 2017 at 5:57 AM, Peter Eisentraut >> <peter.eisentr...@2ndquadrant.com> wrote: >>> I think a more robust way would be to parse >>> Makefile.global, perhaps by a function in TestLib, so it can be reused >>> in other tests. (Even more robust would be to write out an actual Perl >>> file with configuration information somewhere, but maybe we don't need >>> to go there yet.) Or maybe have the respective make variables exported >>> when make check is called (could be included in the prove_check >>> variable?). Anyway, some more pondering could lead to a more general >>> solution. >> >> There is always room for improvement, > > I interpret that as that you are not working on that right now, so I've > closed this patch.
Indeed, I have no plans for that now. There are enough patches to look at these days. My apologies for not making that clear. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
