Re: Planner issue - Mailing list pgsql-performance

From Ragnar Hafstað
Subject Re: Planner issue
Date
Msg-id 1111522143.7726.48.camel@localhost.localdomain
Whole thread Raw
In response to Re: Planner issue  (Alex Turner <armtuk@gmail.com>)
List pgsql-performance
On Tue, 2005-03-22 at 14:36 -0500, Alex Turner wrote:

> I will use an index 220-300, but not 200-300.
> ...
>  Seq Scan on propmain  (cost=0.00..15517.56 rows=6842 width=4) (actual
> time=0.039..239.760 rows=6847 loops=1)
> ...
>  Index Scan using propmain_listprice_i on propmain
> (cost=0.00..22395.95 rows=6842 width=4) (actual time=0.084..25.751
> rows=6847 loops=1)

the rows estimates are accurate, so it is not a question of statistics
anymore.

first make sure effective_cache_size is correctly set, and then
if that is not enough, you might try to lower random_page_cost a bit


gnari



pgsql-performance by date:

Previous
From: Alex Turner
Date:
Subject: Re: Planner issue
Next
From: "Brandon Metcalf"
Date:
Subject: PostgreSQL on Solaris 8 and ufs