2010/7/30 Greg Stark <gsst...@mit.edu>: > On Fri, Jul 30, 2010 at 11:24 AM, Vincenzo Romano > <vincenzo.rom...@notorand.it> wrote: >> At a first glance it seems that for inheritance some bottleneck is >> hindering a full exploit for table partitioning. > > There have been lengthy discussions of how to implement partitioning > to fix these precise problems, yes.
Any reference? >> Is there anyone who knows whether those algorithms are linear or not? > > They're linear in both cases. But they happen at plan time rather than > query execution time. So if your application prepares all its queries > and then uses them many times it would not slow down query execution > but would slow down the query planning time. In some applications this > is much better but in others unpredictable run-times is as bad as long > run-times. Hmmm ... maybe I'm missing the inner meaning of your remarks, Greg. By using PREPARE I run the query planned sooner and I should use the plan with the later execution. You can bet that some of the PREPAREd query variables will pertain to either the child table's CHECK contraints (for table partitions) or to the partial index's WHERE condition (for index partitioning). It's exactly this point (execution time) where the "linearity" will kill the query over a largely partitioned table. Is this what you meant? :-) > Also in the case of having many partial indexes it would slow down > inserts and updates as well, though to a lesser degree, and that would > happen at execution time. This makes fully sense to me. -- Vincenzo Romano at NotOrAnd Information Technologies Software Hardware Networking Training Support Security -- NON QVIETIS MARIBVS NAVTA PERITVS -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
