| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: expanding inheritance in partition bound order |
| Date: | 2017-09-13 10:02:27 |
| Message-ID: | d98d4761-5071-1762-501e-0e15047c714b@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/09/11 18:56, Amit Langote wrote:
> Attached updated patch does it that way for both partitioned table indexes
> and leaf partition indexes. Thanks for pointing it out.
It seems to me we don't really need the first patch all that much. That
is, let's keep PartitionDispatchData the way it is for now, since we don't
really have any need for it beside tuple-routing (EIBO as committed didn't
need it for one). So, let's forget about "decoupling
RelationGetPartitionDispatchInfo() from the executor" thing for now and
move on.
So, attached is just the patch to make RelationGetPartitionDispatchInfo()
traverse the partition tree in depth-first manner to be applied on HEAD.
Thoughts?
Thanks,
Amit
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Make-RelationGetPartitionDispatch-expansion-order-de.patch | text/plain | 10.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2017-09-13 10:08:33 | Re: Supporting huge pages on Windows |
| Previous Message | Amit Khandekar | 2017-09-13 09:52:02 | Re: Partition-wise join for join between (declaratively) partitioned tables |