Re: Indices types, what to use. Btree, Hash, Gin or Gist - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Indices types, what to use. Btree, Hash, Gin or Gist
Date
Msg-id dcc563d10901311711q8b80ec5ieb5fbc464fd4ee19@mail.gmail.com
Whole thread Raw
In response to Re: Indices types, what to use. Btree, Hash, Gin or Gist  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-general
On Sat, Jan 31, 2009 at 1:33 PM, Gregory Stark <stark@enterprisedb.com> wrote:
> No index is going to be particularly effective for boolean columns unless
> they're very heavily skewed. You might find it useful to build separate
> partial indexes on other keys for each value though.

Not entirely true.  If you've got a table where <1% of the rows are
one or the other, a partial index can be very useful on a bool.

Also, in the very odd case where you almost all the time select all
the true or all the false, a regular index can be useful for
reindexing the table on.

But yeah, if there's a relatively even mix of true and false, then a
bool index isn't much use.

pgsql-general by date:

Previous
From: Kevin Murphy
Date:
Subject: Re: Indices types, what to use. Btree, Hash, Gin or Gist
Next
From: Jasen Betts
Date:
Subject: Re: how to implement a foreign key type constraint against a not unique column