| From: | solai v <solai(dot)cdac(at)gmail(dot)com> |
|---|---|
| To: | Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Remove the refint contrib module (for v20) |
| Date: | 2026-06-25 11:28:36 |
| Message-ID: | CAF0whudX1fWrnp5Qm5uU2C+0AK2Agaa+NhnLou3rrCh5DQ-JiQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Ayush,
I tested the v3 patch series on current HEAD.
For v3-0001, i verified that the refint extension files were removed
from contrib/spi, the related build system entries were updated, and
PostgreSQL built successfully after applying the patch. I also
confirmed that CREATE EXTENSION refint fails in a fresh database as
expected once the extension is removed.
For v3-0002, i verified that the patch applied cleanly and reviewed
the changes in AdjustUpgrade.pm. The added handling for upgrades from
versions older than v20, including dropping the refint extension and
its associated test tables during upgrade testing, looks correct. The
tree also built successfully with this patch applied.
I did not perform an actual cross-version pg_upgrade test, but the
patch series applied cleanly and behaved as expected in my testing.
Regards,
solai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nishant Sharma | 2026-06-25 11:31:36 | Re: Show hashed SAOP decision in EXPLAIN |
| Previous Message | Amit Kapila | 2026-06-25 11:27:00 | Re: Proposal: Conflict log history table for Logical Replication |