> Partitions
> ==========
> Next stage would be teaching the planner. The conditions would be
> pseudo-constraints on the partitions. Hence if the conditions and the
> constraints form a non-intersecting set, you can skip that partition
> altogether.
Make that "normal check constraints", and make the planner consider
constraints,
and I think that by itself combined with the current featureset will
be much more powerful than any of the "partitioning" features out there.
(This is mainly needed to optimize selects on the big union all view)
Imho if a dba starts to partition, he usually needs to be more involved
than the average user, so I think he should be able cope with compexity.
What imho would help, is a tool that generates a suggested rule set,
indexes
and actions, which the dba can review and apply. I do not think new SQL
syntax
would really help, since that would somehow hide the great existing
power of
the rule system. A tool would teach the dba, and empower him to use it.
And yes, creating several smaller tables and adding the appropriate
rules
usually makes the VLDB life much easier compared to growing single
tables into
the TB range.
Andreas
