mirror of
https://github.com/postgres/postgres.git
synced 2025-07-08 11:42:09 +03:00
Improve run-time partition pruning to handle any stable expression.
The initial coding of the run-time-pruning feature only coped with cases where the partition key(s) are compared to Params. That is a bit silly; we can allow it to work with any non-Var-containing stable expression, as long as we take special care with expressions containing PARAM_EXEC Params. The code is hardly any longer this way, and it's considerably clearer (IMO at least). Per gripe from Pavel Stehule. David Rowley, whacked around a bit by me Discussion: https://postgr.es/m/CAFj8pRBjrufA3ocDm8o4LPGNye9Y+pm1b9kCwode4X04CULG3g@mail.gmail.com
This commit is contained in:
@ -2175,10 +2175,13 @@ _copyPartitionPruneInfo(const PartitionPruneInfo *from)
|
||||
COPY_NODE_FIELD(pruning_steps);
|
||||
COPY_BITMAPSET_FIELD(present_parts);
|
||||
COPY_SCALAR_FIELD(nparts);
|
||||
COPY_SCALAR_FIELD(nexprs);
|
||||
COPY_POINTER_FIELD(subnode_map, from->nparts * sizeof(int));
|
||||
COPY_POINTER_FIELD(subpart_map, from->nparts * sizeof(int));
|
||||
COPY_BITMAPSET_FIELD(extparams);
|
||||
COPY_BITMAPSET_FIELD(execparams);
|
||||
COPY_POINTER_FIELD(hasexecparam, from->nexprs * sizeof(bool));
|
||||
COPY_SCALAR_FIELD(do_initial_prune);
|
||||
COPY_SCALAR_FIELD(do_exec_prune);
|
||||
COPY_BITMAPSET_FIELD(execparamids);
|
||||
|
||||
return newnode;
|
||||
}
|
||||
|
Reference in New Issue
Block a user