Peter Eisentraut a40fdf6588 Reject child partition FDWs in FOR PORTION OF ... We should defer validating FDW usage until after analysis. We have to guard against not just the topmost table, but also individual child partitions. Added the check to CheckValidResultRel, because it is called after looking up child partitions (accounting for pruning), but before the FDW can run a DirectModify update, which would bypass per-tuple executor work. Author: jian he <jian.universality@gmail.com> Reported-by: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Paul A. Jungwirth <pj@illuminatedcomputing.com> Discussion: https://www.postgresql.org/message-id/flat/CA%2BrenyUte0_UJsJiDJQi82oaBsMJn%3Dcct0Wn%3DvOqXtuDn%3DYYJA%40mail.gmail.com		2026-06-27 19:36:51 +02:00
..
eval_plan_qual.out	postgres_fdw: Add more test coverage for EvalPlanQual testing.	2025-11-06 12:15:00 +09:00
postgres_fdw.out	Reject child partition FDWs in FOR PORTION OF	2026-06-27 19:36:51 +02:00
query_cancel.out	postgres_fdw: re-issue cancel requests a few times if necessary.	2024-12-23 15:14:30 -05:00
query_cancel_1.out	postgres_fdw: Split out the query_cancel test to its own file	2024-07-22 12:49:57 +02:00