Re: pgsql: Add basic TAP test setup for pg_upgrade

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add basic TAP test setup for pg_upgrade
Date: 2017-09-20 16:18:23
Message-ID: 6354.1505924303@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Add basic TAP test setup for pg_upgrade
> The plan is to convert the current pg_upgrade test to the TAP
> framework. This commit just puts a basic TAP test in place so that we
> can see how the build farm behaves, since the build farm client has some
> special knowledge of the pg_upgrade tests.

I hope you're not planning to leave it like this very long. The
pg_upgrade test is already one of the longest steps in the buildfarm
runs, and now we're doing it twice.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-09-20 17:52:43 pgsql: Improve dubious memory management in pg_newlocale_from_collation
Previous Message Alvaro Herrera 2017-09-20 15:39:03 Re: pgsql: Fix erroneous documentation about noise word GROUP.

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2017-09-20 16:18:46 Re: Varying results when using merge joins over postgres_fdw vs hash joins
Previous Message Stephen Frost 2017-09-20 16:10:19 Re: [HACKERS] USER Profiles for PostgreSQL