mirror of
https://github.com/postgres/postgres.git
synced 2025-06-16 06:01:02 +03:00
Move PartitioPruneInfo out of plan nodes into PlannedStmt
The planner will now add a given PartitioPruneInfo to PlannedStmt.partPruneInfos instead of directly to the Append/MergeAppend plan node. What gets set instead in the latter is an index field which points to the list element of PlannedStmt.partPruneInfos containing the PartitioPruneInfo belonging to the plan node. A later commit will make AcquireExecutorLocks() do the initial partition pruning to determine a minimal set of partitions to be locked when validating a plan tree and it will need to consult the PartitioPruneInfos referenced therein to do so. It would be better for the PartitioPruneInfos to be accessible directly than requiring a walk of the plan tree to find them, which is easier when it can be done by simply iterating over PlannedStmt.partPruneInfos. Author: Amit Langote <amitlangote09@gmail.com> Discussion: https://postgr.es/m/CA+HiwqFGkMSge6TgC9KQzde0ohpAycLQuV7ooitEEpbKB0O_mg@mail.gmail.com
This commit is contained in:
@ -82,7 +82,7 @@ ExecInitMergeAppend(MergeAppend *node, EState *estate, int eflags)
|
||||
mergestate->ps.ExecProcNode = ExecMergeAppend;
|
||||
|
||||
/* If run-time partition pruning is enabled, then set that up now */
|
||||
if (node->part_prune_info != NULL)
|
||||
if (node->part_prune_index >= 0)
|
||||
{
|
||||
PartitionPruneState *prunestate;
|
||||
|
||||
@ -93,7 +93,8 @@ ExecInitMergeAppend(MergeAppend *node, EState *estate, int eflags)
|
||||
*/
|
||||
prunestate = ExecInitPartitionPruning(&mergestate->ps,
|
||||
list_length(node->mergeplans),
|
||||
node->part_prune_info,
|
||||
node->part_prune_index,
|
||||
node->apprelids,
|
||||
&validsubplans);
|
||||
mergestate->ms_prune_state = prunestate;
|
||||
nplans = bms_num_members(validsubplans);
|
||||
|
Reference in New Issue
Block a user