Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test
Date
Msg-id da86e561-d974-2293-04f2-38672db3a858@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test
Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test
List pgsql-hackers
On 4/14/17 02:00, Michael Paquier wrote:
> Attached is an updated patch to use --no-sync with pg_dumpall calls.

Please send a rebased patch.

I propose splitting the single Perl script into three separate test
files: one for basic command-line option handling and so on (I would
like to expand that later), one for the main upgrade test, and one for
the funny database names tests.

In the testing file, you removed the paragraph that explains how to do
cross-version upgrade testing.  It's unfortunate that we would lose that
functionality.  What can we do about that?

We also need to have a plan for handling the build farm.  Maybe keep the
vcregress.pl upgradecheck target as a thin wrapper for the time being?

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] <> join selectivity estimate question
Next
From: Alexander Korotkov
Date:
Subject: [HACKERS] Fix bloom WAL tap test