Horton

Re: UPDATE of partition key

Amit Khandekar <amitdkhan.pg@gmail.com>

View thread View on postgr.es
From: Amit Khandekar <amitdkhan.pg@gmail.com>
To: David Fetter <david@fetter.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-02-15T07:36:32Z
Lists: pgsql-hackers 
On 14 February 2017 at 22:24, David Fetter <david@fetter.org> wrote:
> On Mon, Feb 13, 2017 at 05:31:56PM +0530, Amit Khandekar wrote:
>> Currently, an update of a partition key of a partition is not
>> allowed, since it requires to move the row(s) into the applicable
>> partition.
>>
>> Attached is a WIP patch (update-partition-key.patch) that removes
>> this restriction. When an UPDATE causes the row of a partition to
>> violate its partition constraint, then a partition is searched in
>> that subtree that can accommodate this row, and if found, the row is
>> deleted from the old partition and inserted in the new partition. If
>> not found, an error is reported.
>
> This is great!
>
> Would it be really invasive to HINT something when the subtree is a
> proper subtree?

I am not quite sure I understood this question. Can you please explain
it a bit more ...

Commits

  1. Avoid referencing off the end of subplan_partition_offsets.

  2. Allow UPDATE to move rows between partitions.

  3. Remove useless lookup of root partitioned rel in ExecInitModifyTable().

  4. Factor error generation out of ExecPartitionCheck.

  5. Minor preparatory refactoring for UPDATE row movement.

  6. Simplify and encapsulate tuple routing support code.

  7. Avoid coercing a whole-row variable that is already coerced.

  8. Use ResultRelInfo ** rather than ResultRelInfo * for tuple routing.

  9. Make RelationGetPartitionDispatchInfo expand depth-first.

  10. Expand partitioned tables in PartDesc order.

  11. Use a real RT index when setting up partition tuple routing.

  12. Fix transition tables for partition/inheritance.

  13. Fix confusion about number of subplans in partitioned INSERT setup.

  14. Prevent BEFORE triggers from violating partitioning constraints.

  15. Fire per-statement triggers on partitioned tables.

  16. Fix reporting of violations in ExecConstraints, again.

  17. Don't scan partitioned tables.

  18. Allow FDWs to push down quals without breaking EvalPlanQual rechecks.