Re: Forcing index scan on query produces 16x faster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Christian Brink <cbrink@xxxxxxxxxxxx> writes:
> Is there a way to rewrite or hint the planner to get me the better plan 
> without resorting to 'enable_seqscan' manipulation (or am I missing 
> something)?

I think your problem is here:

>   PostgreSQL 8.0.3 on i386-redhat-linux-gnu, compiled by GCC 
> i386-redhat-linux-gcc (GCC) 4.0.0 20050505 (Red Hat 4.0.0-4)

Recent versions are significantly smarter about grouping operations
than that dinosaur.

(Even if you must stay on 8.0.x, you should at least be running
8.0.something-recent; what you have is full of security and data-loss
risks.  8.0.24 was released this week.)

			regards, tom lane

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux