Horton

RE: speeding up planning with partitions

Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>

View thread View on postgr.es
From: "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
To: 'Amit Langote' <Langote_Amit_f8@lab.ntt.co.jp>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-08-30T01:45:43Z
Lists: pgsql-hackers 
From: Amit Langote [mailto:Langote_Amit_f8@lab.ntt.co.jp]
> We can definitely try, but I'm not immediately sure if the further
> improvements will come from continuing to fix the planner.  Maybe, the
> overhead of partitioning could be attributed to other parts of the system.

> Actually, I wrote that for patch 0002.  The next patch (0003) is meant to
> fix that.  So, the overhead you're seeing is even after making sure that
> only the selected partitions are locked.

Thanks for telling your thought.  I understood we should find the bottleneck with profiling first.


Regards
Takayuki Tsunakawa

Commits

  1. Clean up handling of constraint_exclusion and enable_partition_pruning.

  2. Add test case exercising formerly-unreached code in inheritance_planner.

  3. Speed up planning when partitions can be pruned at plan time.

  4. Avoid crash in partitionwise join planning under GEQO.

  5. Avoid passing query tlist around separately from root->processed_tlist.

  6. Build "other rels" of appendrel baserels in a separate step.

  7. Get rid of duplicate child RTE for a partitioned table.

  8. Rearrange make_partitionedrel_pruneinfo to avoid work when we can't prune.

  9. Don't copy PartitionBoundInfo in set_relation_partition_info.

  10. Move building of child base quals out into a new function

  11. Reorganize planner code moved in b60c39759908

  12. Move inheritance expansion code into its own file

  13. Fix inherited UPDATE/DELETE with UNION ALL subqueries.

  14. Rearrange planner to save the whole PlannerInfo (subroot) for a subquery.