Skip site navigation (1) Skip section navigation (2)

Re: bad planning with 75% effective_cache_size

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: bad planning with 75% effective_cache_size
Date: 2012-04-19 00:44:42
Message-ID: 4F8F5FFA.6020800@agliodbs.com (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-performance by date

Next:From: Ants AasmaDate: 2012-04-19 10:32:50
Subject: Re: bad planning with 75% effective_cache_size
Previous:From: Josh BerkusDate: 2012-04-19 00:09:29
Subject: Re: Linux machine aggressively clearing cache

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group