From: | Robert Haas <rhaas(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Make RelationGetPartitionDispatchInfo expand depth-first. |
Date: | 2017-09-14 16:36:57 |
Message-ID: | E1dsX8L-0001Pt-H2@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Make RelationGetPartitionDispatchInfo expand depth-first.
With this change, the order of leaf partitions as returned by
RelationGetPartitionDispatchInfo should now be the same as the
order used by expand_inherited_rtentry. This will make it simpler
for future patches to match up the partition dispatch information
with the planner data structures. The new code is also, in my
opinion anyway, simpler and easier to understand.
Amit Langote, reviewed by Amit Khandekar. I also reviewed and
made a few cosmetic revisions.
Discussion: http://postgr.es/m/d98d4761-5071-1762-501e-0e15047c714b@lab.ntt.co.jp
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/77b6b5e9ceca04dbd6f0f6cd3fc881519acc8714
Modified Files
--------------
src/backend/catalog/partition.c | 252 ++++++++++++++-------------------
src/backend/optimizer/prep/prepunion.c | 7 +
2 files changed, 116 insertions(+), 143 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-09-14 16:59:46 | Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |
Previous Message | Peter Eisentraut | 2017-09-14 16:09:23 | pgsql: Fix bool/int type confusion |