Postgres Pro
Downloads
Home   >   mailing lists

Re: how to enforce index sub-select over filter+seqscan - Mailing list pgsql-performance

From Robert Haas
Subject Re: how to enforce index sub-select over filter+seqscan
Date
Msg-id AANLkTinnz5sUHjcDYo4eYF_LZq6QhZZjU5xJLDjxjM88@mail.gmail.com
Whole thread Raw
In response to how to enforce index sub-select over filter+seqscan  (Dmitry Teslenko <dteslenko@gmail.com>)
List pgsql-performance
Tree view 
On Thu, Sep 23, 2010 at 10:26 AM, Dmitry Teslenko <dteslenko@gmail.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

pgsql-performance by date:

Previous
From: Greg Smith
Date:
Subject: Re: Memory speed testing
Next
From: Dave Crooke
Date:
Subject: Odd behaviour with redundant CREATE statement