Re: reducing random_page_cost from 4 to 2 to force index scan - Mailing list pgsql-performance

From Tom Lane
Subject Re: reducing random_page_cost from 4 to 2 to force index scan
Date
Msg-id 2823.1305314437@sss.pgh.pa.us
Whole thread Raw
In response to Re: reducing random_page_cost from 4 to 2 to force index scan  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: reducing random_page_cost from 4 to 2 to force index scan  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-performance
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Apr 26, 2011 at 9:04 PM, Merlin Moncure <mmoncure@gmail.com> wrote:
>> The very first thing to check is effective_cache_size and to set it to
>> a reasonable value.

> Actually, effective_cache_size has no impact on costing except when
> planning a nested loop with inner index scan.  So, a query against a
> single table can never benefit from changing that setting.

That's flat out wrong.  It does affect the cost estimate for plain
indexscan (and bitmap indexscan) plans.

            regards, tom lane

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PERFORMANCE] expanding to SAN: which portion best to move
Next
From: Robert Haas
Date:
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan