Re: planner index choice - Mailing list pgsql-performance

From tv@fuzzy.cz
Subject Re: planner index choice
Date
Msg-id 2727.85.161.90.190.1280402094.squirrel@sq.gransy.com
Whole thread Raw
In response to Re: planner index choice  (Chris <dmagick@gmail.com>)
Responses Re: planner index choice
List pgsql-performance
> http://explain.depesz.com/s/br9
> http://explain.depesz.com/s/gxH

Well, I don't have time to do a thorough analysis right now, but in all
the plans you've posted there are quite high values in the "Rows x" column
(e.g. the 5727.5 value).

That means a significant difference in estimated and actual row number,
which may lead to poor choice of indexes etc. The planner may simply think
the index is better due to imprecise statistics etc.

Try to increase te statistics target for the columns, e.g.

ALTER TABLE table ALTER COLUMN column SET STATISTICS integer

where "integer" is between 0 and 1000 (the default value is 10 so use 100
or maybe 1000), run analyze and try to run the query again.

Tomas


pgsql-performance by date:

Previous
From: Chris
Date:
Subject: Re: planner index choice
Next
From: Michael Stone
Date:
Subject: Re: Testing Sandforce SSD