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

Re: reducing random_page_cost from 4 to 2 to force index scan

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Sok Ann Yap <sokann(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
Date: 2011-04-27 07:23:32
Message-ID: BANLkTi=_UqUNumJgrc+kV6MbOmtw+grzCQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Wed, Apr 27, 2011 at 9:22 AM, Claudio Freire <klaussfreire(at)gmail(dot)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.

In response to

pgsql-performance by date

Next:From: Kevin GrittnerDate: 2011-04-27 12:40:58
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
Previous:From: Claudio FreireDate: 2011-04-27 07:22:31
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan

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