From: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: On Scalability |
Date: | 2010-10-07 14:33:13 |
Message-ID: | AANLkTi=vq6f7gERj6zKJbKg-ewKAqYaSzcmO0Qog3yn5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
2010/10/7 Stephen Frost <sfrost(at)snowman(dot)net>:
> * Vincenzo Romano (vincenzo(dot)romano(at)notorand(dot)it) wrote:
>> I see the main problem in the way the planner "understands" which partition
>> is useful and which one is not.
>> Having the DDL supporting the feature could just be syntactic sugar
>> if the underlying mechanism is inadequate.
>
> I'm pretty sure the point with the DDL would be to have a way for the
> user to communicate to the planner more understanding about the
> partitioning, not just to be syntactic sugar. With that additional
> information, the planner can make a faster and better decision.
>
> Stephen
Which kind of information are you thinking about?
I think that the stuff you put into the CHECK condition for the table
will say it all.
Infact there you have not just the column names with relevant values, but the
actual expression(s) to be checked,
--
Vincenzo Romano at NotOrAnd Information Technologies
Software Hardware Networking Training Support Security
--
NON QVIETIS MARIBVS NAVTA PERITVS
From | Date | Subject | |
---|---|---|---|
Next Message | Vincenzo Romano | 2010-10-07 14:44:34 | Re: On Scalability |
Previous Message | Greg Smith | 2010-10-07 14:32:38 | Re: On Scalability |
From | Date | Subject | |
---|---|---|---|
Next Message | Vincenzo Romano | 2010-10-07 14:44:34 | Re: On Scalability |
Previous Message | Greg Smith | 2010-10-07 14:32:38 | Re: On Scalability |