* Vincenzo Romano (vincenzo.romano@notorand.it) wrote:
> 2010/10/7 Stephen Frost <sfrost@snowman.net>:
> > * Vincenzo Romano (vincenzo.romano@notorand.it) wrote:
> > The problem is that CHECK conditions can contain just about anything,
> > hence the planner needs to deal with that possibility.
>
> Not really. For partitioning there would be some constraints as you
> have in the DEFAULT values.
How do we know when it's partitioning and not a CHECK constraint being
used for something else..? I'll tell you- through the user using
specific partitioning DDL statements.
> Consuming computing resources at DDL-time should be OK if that will
> lead to big savings at DML-time (run-time), my opinion. It'd be just like
> compile time optimizations.
CHECK constraints, inheiritance, etc, are general things which can be
used for more than just partitioning. Abusing them to go through tons
of extra gyrations to make the specific partitioning case faster at DML
time (if that's really even possible... I'm not convinced you could
make it bullet-proof) isn't a good approach.
Thanks,
Stephen
