Horton

Re: Improve TAP tests of pg_upgrade for cross-version tests

Justin Pryzby <pryzby@telsasoft.com>

View thread View on postgr.es
From: Justin Pryzby <pryzby@telsasoft.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org, Andrew Dunstan <andrew@dunslane.net>, Robert Haas <robertmhaas@gmail.com>
Date: 2022-07-29T21:15:26Z
Lists: pgsql-hackers

Attachments

On Wed, Jul 06, 2022 at 03:27:28PM +0900, Michael Paquier wrote:
> On Thu, Jun 09, 2022 at 04:49:01PM +0900, Michael Paquier wrote:
> > Rebased to cope with the recent changes in this area.
> 
> Please find attached an updated version of this patch, where I have
> extended the support of the upgrade script down to 9.5 as origin
> version, as ~9.4 now fail because of cluster_name, so Cluster.pm does
> not support that.  FWIW, I have created an extra set of dumps down to
> 9.4.

This was using the old psql rather than the new one.
Before v10, psql didn't have \if.

I think Cluster.pm should be updated to support the upgrades that upgrade.sh
supported.  I guess it ought to be fixed in v15.

-- 
Justin

Commits

  1. Add filtering capability for cross-version pg_upgrade tests