Re: Re: Rewriting the test of pg_upgrade as a TAP test - take two

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: David Steele <david(at)pgmasters(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Rewriting the test of pg_upgrade as a TAP test - take two
Date: 2018-03-22 01:42:35
Message-ID: CAMsr+YE2H+BULrLr+8OJKxKVS=d7PuUqHPWRESs_ncaN=Was3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22 March 2018 at 09:39, Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Wed, Mar 21, 2018 at 10:51:04AM -0400, David Steele wrote:
> > On 3/6/18 4:12 PM, Tom Lane wrote:
> > It seems the consensus is that we'll need a build farm update before we
> > can move forward with the patch and that we don't need to wait long for
> > people to upgrade.
> >
> > Andrew, do you have a date for the next release?
>
> Even if a lighter version of this patch stripped from multi-version
> support (Who uses that actually?)

I'm super excited by the idea of multi-version support in TAP, if that's
what you mean.

Why? Because I use TAP heavily in extensions. Especially replication
extensions. Which like to talk across multiple versions. I currently need
external test frameworks and some hideous hacks to do this.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-03-22 01:49:57 Re: Re: Rewriting the test of pg_upgrade as a TAP test - take two
Previous Message Michael Paquier 2018-03-22 01:42:20 Re: [HACKERS] taking stdbool.h into use