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

From Peter Eisentraut
Subject Re: [PATCH] Fix null pointer dereference in PG19
Date
Msg-id 31b38752-d16f-465f-9e85-b01e6da9d36c@eisentraut.org
Whole thread
In response to Re: [PATCH] Fix null pointer dereference in PG19  (Paul A Jungwirth <pj@illuminatedcomputing.com>)
List pgsql-hackers
On 09.07.26 17:22, Paul A Jungwirth wrote:
> Checking at v1 is Aleksander's original patch. Then v2 adds tests that
> crash the server. v3 moves the check to rewrite time, and the tests
> pass. v4 moves the check again to exec time. But v4 is a behavior
> change: an UPDATE that touches zero rows no longer fails. I thought
> that was weird; that's why I recommended leaving it out (in
> https://www.postgresql.org/message-id/ 
> CA%2BrenyXPEJYOVov3XtzTp3NusGkObc9UeW-Nm78K8_nsWSnnfg%40mail.gmail.com
> before I added the crashing tests).

I committed patches 0001 through 0003 (squashed).

I think I was mistaken about the need for an executor check (patch 
0004).  But we can add it on if a need appears.



pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: sequencesync worker race with REFRESH SEQUENCES
Next
From: Kwangwon Seo
Date:
Subject: [PATCH] Fix quotation logic for unreserved keywords in window specifications