On Sep 1, 2010, at 4:10 PM, Tom Lane wrote:
> Boszormenyi Zoltan <zb@cybertec.at> writes:
>> we are experimenting with modifying table partitioning
>> so the ORDER BY clause can be pushed down to
>> child nodes on the grounds that:
>
> This is really premature, and anything you do along those lines now will
> probably never get committed. The problem is that the transformation
> you propose is wrong unless the planner can prove that the different
> child tables contain nonoverlapping ranges of the sort key. Now you
> might be intending to add logic to try to prove that from inspection of
> constraints, but I don't believe that reverse-engineering such knowledge
> on the fly is a sane approach: it will be hugely expensive and will add
> that cost even in many situations where the optimization fails to apply.
>
well, why non-overlapping? the idea is to make append smart enough to take the sorted lists from below and merge them
whichwill give sorted output as well.
my original idea was what you described but given Martijn van Oosterhout's posting we were pretty confident that we can
getalong without non-overlapping partitions.
> The project direction is that we are going to add some explicit
> representation of partitioned tables. After that, the planner can just
> know immediately that a range-partitioned sort key is amenable to this
> treatment, and at that point it'll make sense to work on it.
>
can you outline some ideas here and maybe point to some useful discussion here?
many thanks,
hans
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de
