Re: bad planning with 75% effective_cache_size - Mailing list pgsql-performance

From Josh Berkus
Subject Re: bad planning with 75% effective_cache_size
Date
Msg-id 4F8F5FFA.6020800@agliodbs.com
Whole thread Raw
In response to Re: bad planning with 75% effective_cache_size  (Istvan Endredy <istvan.endredy@gmail.com>)
Responses Re: bad planning with 75% effective_cache_size  (Ants Aasma <ants@cybertec.at>)
List pgsql-performance
On 4/17/12 2:49 AM, Istvan Endredy wrote:
> Hi,
>
> thanks for the suggestion, but it didn't help. We have tried it earlier.
>
> 7500ms
> http://explain.depesz.com/s/ctn

This plan seems very odd -- doing individual index lookups on 2.8m rows
is not standard planner behavior.  Can you confirm that all of your
other query cost parameters are the defaults?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Linux machine aggressively clearing cache
Next
From: Ants Aasma
Date:
Subject: Re: bad planning with 75% effective_cache_size