| From: | Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove the refint contrib module (for v20) |
| Date: | 2026-06-29 08:05:25 |
| Message-ID: | CAJTYsWWb6tPKoCcBg-_wHaSYFTMEHgvr9p6xH0y+Rqu-_Qx0Vg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Mon, 29 Jun 2026 at 11:53, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> 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?
Thanks for the review!
Addressed in this thread:
https://www.postgresql.org/message-id/CAJTYsWVMX_csjBafWngAqAAXBa%3D%2BUy%2BrY2Je4jM6CJ11tF38Mw%40mail.gmail.com
Regards,
Ayush
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2026-06-29 08:14:11 | Re: use of SPI by postgresImportForeignStatistics |
| Previous Message | Ayush Tiwari | 2026-06-29 08:02:02 | Re: Remove the refint contrib module (for v20) |