| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> |
| Cc: | pierre(dot)forstmann(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19476: Segmentation fault in contrib/spi |
| Date: | 2026-05-14 16:45:46 |
| Message-ID: | agX8Olw7JnK7o9se@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-refint-Fix-seg-fault-in-check_foreign_key.patch | text/plain | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayush Tiwari | 2026-05-14 17:12:07 | Re: BUG #19476: Segmentation fault in contrib/spi |
| Previous Message | Nathan Bossart | 2026-05-14 16:01:55 | Re: BUG #19476: Segmentation fault in contrib/spi |