Re: PG8.2.1 choosing slow seqscan over idx scan - Mailing list pgsql-performance

From Tom Lane
Subject Re: PG8.2.1 choosing slow seqscan over idx scan
Date
Msg-id 26412.1168983547@sss.pgh.pa.us
Whole thread Raw
In response to PG8.2.1 choosing slow seqscan over idx scan  ("Jeremy Haile" <jhaile@fastmail.fm>)
Responses Re: PG8.2.1 choosing slow seqscan over idx scan  ("Jeremy Haile" <jhaile@fastmail.fm>)
List pgsql-performance
"Jeremy Haile" <jhaile@fastmail.fm> writes:
> Running PostgreSQL 8.2.1 on Win32.   The query planner is choosing a seq
> scan over index scan even though index scan is faster (as shown by
> disabling seqscan).  Table is recently analyzed and row count estimates
> seem to be in the ballpark.

Try reducing random_page_cost a bit.  Keep in mind that you are probably
measuring a fully-cached situation here, if you repeated the test case.
If your database fits into memory reasonably well then that's fine and
you want to optimize for that case ... but otherwise you may find
yourself pessimizing the actual behavior.

            regards, tom lane

pgsql-performance by date:

Previous
From: "Jeremy Haile"
Date:
Subject: PG8.2.1 choosing slow seqscan over idx scan
Next
From: "Jeremy Haile"
Date:
Subject: Re: PG8.2.1 choosing slow seqscan over idx scan