Re: [PATCH] Fix null pointer dereference in PG19 - Mailing list pgsql-hackers

From Paul A Jungwirth
Subject Re: [PATCH] Fix null pointer dereference in PG19
Date
Msg-id CA+renyUoTRnn0o4Pnfy2AOdtqMH3+n29_AfD4Aih3ifwMX9vyA@mail.gmail.com
Whole thread
In response to Re: [PATCH] Fix null pointer dereference in PG19  (Paul A Jungwirth <pj@illuminatedcomputing.com>)
List pgsql-hackers
On Wed, Apr 22, 2026 at 12:42 PM Paul A Jungwirth
<pj@illuminatedcomputing.com> wrote:
>
> Here is v4 of the fix for this. I'd like to continue the conversation
> here since that other thread is huge and attached to the original
> commitfest entry for the feature. I'll make a new CF entry for just
> this thread.
>
> This patch squashes jian he's test enhancements from his v3 patch.
> Also I changed '[2024-01-01,2024-12-31)' to '[2024-01-01,2025-01-01)',
> which look less like a mistake (not that it matters to the test), and
> I cleaned up the test comment a little.

Here is a v5, documenting that we skip all FOR PORTION OF work in case
of an INSTEAD OF trigger.

Yours,

--
Paul              ~{:-)
pj@illuminatedcomputing.com

Attachment

pgsql-hackers by date:

Previous
From: Paul A Jungwirth
Date:
Subject: Re: SQL:2011 Application Time Update & Delete
Next
From: Mok
Date:
Subject: New vacuum config to avoid anti wraparound vacuums