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

From Claudio Freire
Subject Re: reducing random_page_cost from 4 to 2 to force index scan
Date
Msg-id BANLkTi=_UqUNumJgrc+kV6MbOmtw+grzCQ@mail.gmail.com
Whole thread Raw
In response to Re: reducing random_page_cost from 4 to 2 to force index scan  (Claudio Freire <klaussfreire@gmail.com>)
List pgsql-performance
On Wed, Apr 27, 2011 at 9:22 AM, Claudio Freire <klaussfreire@gmail.com> wrote:
> The problem there, I think, is that the planner is doing a full join,
> instead of a semi-join.

Or, rather, computing cost as if it was a full join. I'm not sure why.

pgsql-performance by date:

Previous
From: Claudio Freire
Date:
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
Next
From: "Kevin Grittner"
Date:
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan