Re: how to enforce index sub-select over filter+seqscan

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dmitry Teslenko <dteslenko(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: how to enforce index sub-select over filter+seqscan
Date: 2010-09-27 17:30:03
Message-ID: AANLkTinnz5sUHjcDYo4eYF_LZq6QhZZjU5xJLDjxjM88@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Sep 23, 2010 at 10:26 AM, Dmitry Teslenko <dteslenko(at)gmail(dot)com> wrote:
> I know I can set enable_seqscan = off.
> Is there other ways to enforce index usage?

Not really, but I suspect random_page_cost and seq_page_cost might
help the planner make better decisions. Is your data by any chance
mostly cached in memory?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Dave Crooke 2010-09-27 18:50:43 Odd behaviour with redundant CREATE statement
Previous Message Greg Smith 2010-09-27 16:53:26 Re: Memory speed testing