From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: On partitioning |
Date: | 2014-09-01 16:12:17 |
Message-ID: | 54049AE1.8010703@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/01/2014 06:59 PM, Tom Lane wrote:
> Greg Stark <stark(at)mit(dot)edu> writes:
>> On Sun, Aug 31, 2014 at 9:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Aside from costing planning time, most likely that would forever prevent
>>> us from pushing some types of intelligence about partitioning into the
>>> executor.
>
>> How would it affect this calculus if there were partitioned indexes
>> which were created on the overall table and guaranteed to exist on
>> each partition that the planner could use -- and then possibly also
>> per-partition indexes that might exist in addition to those?
>
> That doesn't actually fix the planning-time issue at all. Either the
> planner considers each partition individually to create a custom plan
> for it, or it doesn't.
Hmm. Couldn't you plan together all partitions that do have the same
indexes? In other words, create a custom plan for each group of
partitions, rather than each partition?
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Dobes Vandermeer | 2014-09-01 16:50:37 | Re: Tips/advice for implementing integrated RESTful HTTP API |
Previous Message | Andres Freund | 2014-09-01 16:09:27 | Re: On partitioning |