Re: Improving test coverage of extensions with pg_dump

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improving test coverage of extensions with pg_dump
Date: 2015-08-03 02:15:58
Message-ID: CAB7nPqRM73BE7ou84BZ0OWU6r9uwHzXbhjXxhTwoBgpe54y50Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 30, 2015 at 5:35 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Note as well that I will be fine with any decision taken by the
> committer who picks up this, this test case is useful by itself in any
> case.

And I just recalled that I actually did no tests for this thing on
Windows. As this uses the TAP facility, I think that it makes most
sense to run it with tapcheck instead of modulescheck in vcregress.pl
because of its dependency with IPC::Run. The compilation with MSVC is
fixed as well.
--
Michael

Attachment Content-Type Size
0001-Add-TAP-test-for-pg_dump-checking-data-dump-of-exten.patch text/x-diff 6.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2015-08-03 02:20:12 Re: nodes/*funcs.c inconsistencies
Previous Message Michael Paquier 2015-08-03 01:56:53 Re: Explanation for intermittent buildfarm pg_upgradecheck failures