The following bug has been logged online:
Bug reference: 5652
Logged by: Mladen Gogala
Email address: mladen.gog...@vmsinfo.com
PostgreSQL version: 8.4.4
Operating system: Red Hat Linux 5.5, 64b
Description:Optimizer does wrong thing with partitioned tables
Details
Euler Taveira de Oliveira 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
nd you personally 2 versions of a script
that I am still writing, just to see to what extent do I go to get the
necessary performance. Optimizer definitely needs fixes when it comes to
partitions.
--
Mladen Gogala
Sr. Oracle DBA
1500 Broadway
New York, NY 10036
(212) 329-5251
http://www.vms
Jeff Davis wrote:
On Fri, 2010-09-10 at 16:53 -0400, Mladen Gogala wrote:
Jeff, that's the problem. Functions like "MAX" are rather ordinary and
frequently used.
I agree that it could be improved. The best way to move such improvement
forward is to advance the discuss