pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Ignore hash's relallvisible when checking pg_upgrade from pre-v1
Date: Sun, 23 Feb 2025 19:16:33 +0000
Message-ID: <E1tmHSq-000L5L-2a@gemulon.postgresql.org> (raw)

Ignore hash's relallvisible when checking pg_upgrade from pre-v10.

Our cross-version upgrade tests have been failing for some pre-v10
source versions since commit 1fd1bd871.  This turns out to be
because relallvisible may change for tables that have hash indexes,
because the upgrade process forcibly reindexes such indexes to
deal with the changes made in v10.

Fortunately, the set of tables that have such indexes is small
and won't change anymore in those branches.  So just hack up
AdjustUpgrade.pm to not compare the relallvisible values of
those specific tables.

While here, also tighten the regex that suppresses comparison
of version fields.

Discussion: https://postgr.es/m/812817.1740277228@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/fc0d0ce978752493868496be6558fa17b7c4c3cf

Modified Files
--------------
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | 32 ++++++++++++++++++++++----
1 file changed, 28 insertions(+), 4 deletions(-)



Message-ID: <E1tmHSq-000L5L-2a@gemulon.postgresql.org>
Permalink:  ../E1tmHSq-000L5L-2a@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1tmHSq-000L5L-2a@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Ignore hash's relallvisible when checking pg_upgrade from pre-v1
  In-Reply-To: <E1tmHSq-000L5L-2a@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox