Re: bad planning with 75% effective_cache_size

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Istvan Endredy" <istvan(dot)endredy(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: bad planning with 75% effective_cache_size
Date: 2012-04-05 15:41:57
Message-ID: 4F7D76F50200002500046BFA@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Istvan Endredy <istvan(dot)endredy(at)gmail(dot)com> wrote:

> i've ran into a planning problem.

> If effective_cache_size has a greater value (6GB), this select has
> a bad planning and long query time (2000ms):

Could you try that configuration with one change and let us know how
it goes?:

set cpu_tuple_cost = '0.05';

I've seen an awful lot of queries benefit from a higher value for
that setting, and I'm starting to think a change to that default is
in order.

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tomas Vondra 2012-04-05 15:49:56 Re: H800 + md1200 Performance problem
Previous Message Gregg Jaskiewicz 2012-04-05 15:39:26 heavly load system spec