Re: Coverage improvements of src/bin/pg_basebackup and pg_receivewal --endpos

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Coverage improvements of src/bin/pg_basebackup and pg_receivewal --endpos
Date: 2017-09-11 22:21:54
Message-ID: CAB7nPqRrgkmLSqFegKrSe=+DFJXgiLnjbkJGxARguybqLKMmcA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 12, 2017 at 5:57 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> I have committed this patch, after a perltidy run, but the way the libz
> detection was implemented was a bit too hackish for me, so I have
> omitted that for now.

Thanks.

> 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,
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-09-11 22:30:58 Re: PG 10 release notes
Previous Message Bruce Momjian 2017-09-11 22:09:20 Re: PG 10 release notes