On Fri, Sep 10, 2010 at 9:31 AM, Euler Taveira de Oliveira <eu...@timbira.com> wrote: > Mladen Gogala escreveu: >> Optimizer chooses to scan each partitioned table sequentially, instead of >> using the available index: >> > This is not a bug. How would the optimizer know that the maximum value is in > that specific partition? There is neither a global index for a partitioned > table nor an optimizer artifact to know aggregate information before scanning > all of the partitions. Maybe when we have a better support for table > partitioning such optimizer artifact would be implemented but don't hold your > breath.
I wonder if Merge Append could be made to help with this case. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
