From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christian Brink <cbrink@r-stream.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Forcing index scan on query produces 16x faster
Date: Wed, 17 Mar 2010 18:04:25 -0400
Message-ID: <27001.1268863465@sss.pgh.pa.us> (raw)
In-Reply-To: <4BA148CF.5080701@r-stream.com>
References: <4BA148CF.5080701@r-stream.com>
Christian Brink <cbrink@r-stream.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, cbrink@r-stream.com
Subject: Re: Forcing index scan on query produces 16x faster
In-Reply-To: <27001.1268863465@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox