Re: [PATCH] Fix null pointer dereference in PG19

Aleksander Alekseev <aleksander@tigerdata.com>

From: Aleksander Alekseev <aleksander@tigerdata.com>
To: PostgreSQL Development <pgsql-hackers@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter@eisentraut.org>, Paul A Jungwirth <pj@illuminatedcomputing.com>, jian he <jian.universality@gmail.com>
Date: 2026-06-24T11:12:59Z
Lists: pgsql-hackers

Attachments

Hi Peter,

Thanks for your attention to this.

> I don't understand the status of this discussion.  The original bug
> report is related to views and INSTEAD OF triggers.  But the last few
> patches that have been posted here appear to be unrelated to that
> specific issue.

That makes two of us. My humble understanding is that there are
several related discussions but they are happening elsewhere now. Feel
free correcting me if this is not the case.

Here I propose to focus on a particular crash and the particular
proposed bugfix, v1-0001. Perhaps it should be rewritten or maybe we
should reject it in favor of another patch. Both are possible
outcomes. Right now I'm only interested in fixing a particular crash.

> I definitely don't like checking volatility at parse time, though.

So.... the last comment from Tom was that he is not happy :) but I'm
not sure about the actionable items. Tom, could you please elaborate a
bit?

-- 
Best regards,
Aleksander Alekseev