Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Date: 2021-12-15 01:47:24
Message-ID: YblJLJKUZYI4Pqbq@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 13, 2021 at 10:14:49PM -0800, Andres Freund wrote:
> Tom's point was that the buildfarm scripts do
> if ($self->{bfconf}->{using_msvc})
> @checklog = run_log("perl vcregress.pl upgradecheck");
> else
> "cd $self->{pgsql}/src/bin/pg_upgrade && $make $instflags check";
>
> if we don't want to break every buildfarm member that has TestUpgrade enabled
> the moment this is committed, we need to have a backward compat path.

Missed that, thanks! I'll think about all that a bit more before
sending a long-overdue rebased version.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2021-12-15 01:58:32 Re: Life cycles of tuple descriptors
Previous Message Peter Smith 2021-12-15 01:17:37 Re: row filtering for logical replication