Horton

Fix bug in cbc127917 to handle nested Append correctly

Amit Langote <amitlan@postgresql.org>

View on postgr.es
Commit: cbb9086c9ef64b020cb9036f50afc14644bbf734
Author: Amit Langote <amitlan@postgresql.org>
Date: 2025-02-25T00:24:42Z
Releases: 18.0 
Fix bug in cbc127917 to handle nested Append correctly

A non-leaf partition with a subplan that is an Append node was
omitted from PlannedStmt.unprunableRelids because it was mistakenly
included in PlannerGlobal.prunableRelids due to the way
PartitionedRelPruneInfo.leafpart_rti_map[] is constructed. This
happened when a non-leaf partition used an unflattened Append or
MergeAppend.  As a result, ExecGetRangeTableRelation() reported an
error when called from CreatePartitionPruneState() to process the
partition's own PartitionPruneInfo, since it was treated as prunable
when it should not have been.

Reported-by: Alexander Lakhin <exclusion@gmail.com> (via sqlsmith)
Diagnosed-by: Tender Wang <tndrwang@gmail.com>
Reviewed-by: Tender Wang <tndrwang@gmail.com>
Discussion: https://postgr.es/m/74839af6-aadc-4f60-ae77-ae65f94bf607@gmail.com

Files

PathChange+/−
src/backend/executor/execPartition.c modified +9 −4
src/backend/partitioning/partprune.c modified +8 −1
src/test/regress/expected/partition_prune.out modified +48 −0
src/test/regress/sql/partition_prune.sql modified +12 −0

Discussion