Re: expanding inheritance in partition bound order
Amit Langote <langote_amit_f8@lab.ntt.co.jp>
From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Amit Khandekar <amitdkhan.pg@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-30T02:36:19Z
Lists: pgsql-hackers
Attachments
- 0001-Decouple-RelationGetPartitionDispatchInfo-from-execu.patch (text/plain) patch 0001
- 0002-Teach-expand_inherited_rtentry-to-use-partition-boun.patch (text/plain) patch 0002
On 2017/08/29 4:26, Robert Haas wrote: > I think this patch could be further simplified by continuing to use > the existing function signature for RelationGetPartitionDispatchInfo > instead of changing it to return a List * rather than an array. I > don't see any benefit to such a change. The current system is more > efficient. OK, restored the array way. > I keep having the feeling that this is a big patch with a small patch > struggling to get out. Is it really necessary to change > RelationGetPartitionDispatchInfo so much or could you just do a really > minimal surgery to remove the code that sets the stuff we don't need? > Like this: Sure, done in the attached updated patch. Thanks, Amit
Commits
-
Make RelationGetPartitionDispatchInfo expand depth-first.
- 77b6b5e9ceca 11.0 landed
-
Expand partitioned tables in PartDesc order.
- 30833ba154e0 11.0 landed
-
Don't lock tables in RelationGetPartitionDispatchInfo.
- 7c0ca2900f7c 10.0 landed
- 54cde0c4c058 11.0 landed
-
Speed up dropping tables with many partitions.
- c1e0e7e1d790 10.0 cited