Re: will the planner ever use an index when the condition is <> ?

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Roxanne Reid-Bennett <rox(at)tara-lu(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: will the planner ever use an index when the condition is <> ?
Date: 2011-12-18 20:11:28
Message-ID: CABRT9RC7UHCgqhcOi9W5U3wzKpv3H9FWkdZpP0vuKFxbamhb3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sun, Dec 18, 2011 at 16:52, Roxanne Reid-Bennett <rox(at)tara-lu(dot)com> wrote:
> Is there an index type that can check "not equal"?
> This specific column has a limited number of possible values - it is
> essentially an enumerated list.

Instead of writing WHERE foo<>3 you could rewrite it as WHERE foo IN
(1,2,4,...) or WHERE foo < 3 OR foo > 3. Both of these are indexable
queries, but obviously the planner may choose not to use index scan if
it's not worth it.

Regards,
Marti

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Roxanne Reid-Bennett 2011-12-18 20:18:49 Re: will the planner ever use an index when the condition is <> ?
Previous Message Tom Lane 2011-12-18 18:31:26 Re: will the planner ever use an index when the condition is <> ?