Re: UPDATE of partition key
Robert Haas <robertmhaas@gmail.com>
On Fri, Sep 22, 2017 at 1:57 AM, Amit Khandekar <amitdkhan.pg@gmail.com> wrote: > The patch for the above change is : > 0002-Prevent-a-redundant-ConvertRowtypeExpr-node.patch Thinking about this a little more, I'm wondering about how this case arises. I think that for this patch to avoid multiple conversions, we'd have to be calling map_variable_attnos on an expression and then calling map_variable_attnos on that expression again. >>> If I understand correctly, the reason for changing mt_partitions from >>> ResultRelInfo * to ResultRelInfo ** is that, currently, all of the >>> ResultRelInfos for a partitioning hierarchy are allocated as a single >>> chunk, but we can't do that and also reuse the ResultRelInfos created >>> during InitPlan. I suggest that we do this as a preparatory patch. >> >> Ok, will prepare a separate patch. Do you mean to include in that >> patch the changes I did in ExecSetupPartitionTupleRouting() that >> re-use the ResultRelInfo structures of per-subplan update result rels >> ? > > Above changes are in attached > 0001-Re-use-UPDATE-result-rels-created-in-InitPlan.patch. No, not all of those changes. Just the adjustments to make ModifyTableState's mt_partitions be of type ResultRelInfo ** rather than ResultRelInfo *, and anything closely related to that. Not, for example, the num_update_rri stuff. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Avoid referencing off the end of subplan_partition_offsets.
- 945f71db8452 11.0 landed
-
Allow UPDATE to move rows between partitions.
- 2f178441044b 11.0 landed
-
Remove useless lookup of root partitioned rel in ExecInitModifyTable().
- dca48d145e0e 11.0 cited
-
Factor error generation out of ExecPartitionCheck.
- 19c47e7c8202 11.0 landed
-
Minor preparatory refactoring for UPDATE row movement.
- ef6087ee5fa8 11.0 landed
-
Simplify and encapsulate tuple routing support code.
- cc6337d2fed5 11.0 landed
-
Avoid coercing a whole-row variable that is already coerced.
- 1c497fa72df7 11.0 landed
-
Use ResultRelInfo ** rather than ResultRelInfo * for tuple routing.
- 60f7c0abef03 11.0 landed
-
Make RelationGetPartitionDispatchInfo expand depth-first.
- 77b6b5e9ceca 11.0 cited
-
Expand partitioned tables in PartDesc order.
- 30833ba154e0 11.0 cited
-
Use a real RT index when setting up partition tuple routing.
- f81a91db4d1c 10.0 cited
-
Fix transition tables for partition/inheritance.
- 501ed02cf6f4 10.0 cited
-
Fix confusion about number of subplans in partitioned INSERT setup.
- 78a030a44196 10.0 cited
-
Prevent BEFORE triggers from violating partitioning constraints.
- 15ce775faa42 10.0 cited
-
Fire per-statement triggers on partitioned tables.
- e180c8aa8caf 10.0 cited
-
Fix reporting of violations in ExecConstraints, again.
- c0a8ae7be392 10.0 cited
-
Don't scan partitioned tables.
- d3cc37f1d801 10.0 cited
-
Allow FDWs to push down quals without breaking EvalPlanQual rechecks.
- 5fc4c26db512 9.6.0 cited