Re: Remove the refint contrib module (for v20) - Mailing list pgsql-hackers

From Ayush Tiwari
Subject Re: Remove the refint contrib module (for v20)
Date
Msg-id CAJTYsWVofHXC_uPoE_qUCprH=RseLkNHbJyHDH5Jfxf02AErCA@mail.gmail.com
Whole thread
Responses Re: Remove the refint contrib module (for v20)
List pgsql-hackers
Hi,

On Mon, 29 Jun 2026 at 00:29, Daniel Gustafsson <daniel@yesql.se> wrote:
> On 28 Jun 2026, at 10:14, Álvaro Herrera <alvherre@kurilemu.de> wrote:

> The doc patch says that Postgres 19 shipped a contrib module named
> refint, but that's not fully correct.  It shipped an *extension* named
> refint inside the contrib module named spi.  I think that wording could
> be improved.

Agreed.

+    trigger functions <function>check_primary_key()</function> and

We also typically don't append parentheses to function names in the docs.

Thanks for the review!

Attaching patch with improved wording and parentheses
changes.

Basic git diff between v3 and v4:

-  <title>refint Module Removed</title>
+  <title>refint Extension Removed</title>

-    PostgreSQL 19 and below shipped a
-    contrib module named refint that provided the
-    trigger functions check_primary_key() and
-    check_foreign_key() as an early way to enforce
+    PostgreSQL 19 and below shipped an
+    extension named refint, part of the
+    spi contrib module, providing the trigger
+    functions check_primary_key and
+    check_foreign_key as an early way to enforce

-    ...), and the module was removed
+    ...), and the extension was removed

Regards,
Ayush 
Attachment

pgsql-hackers by date:

Previous
From: "cca5507"
Date:
Subject: Re: Handle concurrent drop when doing whole database vacuum
Next
From: JoongHyuk Shin
Date:
Subject: Re: [PATCH] Don't call ereport(ERROR) from recovery target GUC assign hooks