Date: Thu, 14 May 2026 11:45:46 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Ayush Tiwari <ayushtiwari.slg01@gmail.com>
Cc: pierre.forstmann@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19476: Segmentation fault in contrib/spi
Message-ID: <agX8Olw7JnK7o9se@nathan>
References: <19476-bd04ea6241345303@postgresql.org>
 <CAJTYsWVuNPbqS2p1gEitRLBHuytqM7OMawuzVH6g4uqGw4RBsQ@mail.gmail.com>
 <1357efa6-dddb-4e60-ba6f-e88d03a4e010@gmail.com>
 <CAJTYsWWh5qsJcLatT5HD9daTEbCnZUZoqaDPGiT=+EyHkEKJ2A@mail.gmail.com>
 <agXx84rrzKWY9aAE@nathan>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="CN4uTtA78AYCFRt1"
Content-Disposition: inline
In-Reply-To: <agXx84rrzKWY9aAE@nathan>
Archived-At: <https://www.postgresql.org/message-id/agX8Olw7JnK7o9se%40nathan>
Precedence: bulk


--CN4uTtA78AYCFRt1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, May 14, 2026 at 11:01:55AM -0500, Nathan Bossart wrote:
> Regarding 0001, note that the refint docs state the following:
> 
>     Note that the primary/unique key columns should be marked NOT NULL and
>     should have a unique index.
> 
> So maybe we could alternatively teach check_foreign_key() to either ERROR
> or do nothing instead.  On the other hand, given this case seemed to
> accidentally work before the CVE fix, it's arguably worth fixing.

Here is what I have staged for commit, which I intend to do shortly.

-- 
nathan

--CN4uTtA78AYCFRt1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment;
	filename=v3-0001-refint-Fix-seg-fault-in-check_foreign_key.patch