Re: Remove the refint contrib module (for v20)

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: Remove the refint contrib module (for v20)
Date: 2026-06-29 06:23:28
Message-ID: CAHGQGwHmGjbC3eTCO3y_66-U2YRKjKKBDFUXKfrpVLJkNp7teg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 6, 2026 at 4:28 AM Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:
> 0002 (test-only) teaches AdjustUpgrade.pm to drop the refint
> extension and its leftover tables (pkeys, fkeys, fkeys2) from
> contrib_regression_spi / regression_spi when upgrading from a version
> that still shipped refint, so cross-version pg_upgrade tests don't
> fail dump comparison once v20 opens.
> I followed the existing < 19 btree_gist block style.

In make-based contrib tests with USE_MODULE_DB=1, contrib/spi uses
contrib_regression_autoinc database, since autoinc is the first entry
in MODULES. So, in 0002 patch, shouldn't we also remove
the refint-related objects from contrib_regression_autoinc?

For example:

foreach my $dbname (
'contrib_regression_autoinc',
'contrib_regression_spi',
'regression_spi')
{
next unless $dbnames{$dbname};

_add_st(
$result,
$dbname,
'drop extension if exists refint cascade',
'drop table if exists pkeys, fkeys, fkeys2');
}

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2026-06-29 06:29:12 Re: FOR PORTION OF should reject GENERATED columns
Previous Message Michael Paquier 2026-06-29 06:00:42 Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope