| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
| Subject: | Re: [PATCH] Fix null pointer dereference in PG19 |
| Date: | 2026-04-24 04:44:35 |
| Message-ID: | CACJufxFgKVL=NnPocAwhRFqpLHckN3N1Ndf7FjGNTdtsAA26mg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 21, 2026 at 11:24 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> * I'd tend to move the anti-FDW check to execution too.
> It's not actively wrong, since nowadays we don't permit
> relations to change relkind, but it seems out of place.
> Also, it seems inadequate to deal with the case of a target
> that is a partitioned table having FDW partitions.
>
Hi.
Instead of adding another subnode in CheckValidResultRel,
I am passing ModifyTable to it, this will be more future-proof.
| Attachment | Content-Type | Size |
|---|---|---|
| v7-0001-FOR-PORTION-OF-guard-against-FDW.patch | text/x-patch | 8.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-04-24 04:46:51 | Re: Support EXCEPT for TABLES IN SCHEMA publications |
| Previous Message | Henson Choi | 2026-04-24 04:44:26 | SQL/PGQ: Support multi-pattern path matching in GRAPH_TABLE |