Re: Rewriting the test of pg_upgrade as a TAP test

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rewriting the test of pg_upgrade as a TAP test
Date: 2017-09-22 20:48:23
Message-ID: 68eee9f1-864d-a6f8-cbf9-dd9bda6be9be@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/19/17 19:00, Michael Paquier wrote:
> On Wed, Sep 20, 2017 at 7:57 AM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> To get things rolling, I have committed just the basic TAP tests, to
>> give it a spin on the build farm. I'll work through the rest in the
>> coming days.

I have reverted this because of the build farm issue. Putting the patch
on hold in the CF until we have a new plan.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-09-22 21:09:03 Rethinking autovacuum.c memory handling
Previous Message Peter Geoghegan 2017-09-22 20:46:34 Re: CREATE COLLATION does not sanitize ICU's BCP 47 language tags. Should it?