Re: plans for bitmap indexes? - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: plans for bitmap indexes?
Date
Msg-id 20041021201725.GG68407@decibel.org
Whole thread Raw
In response to Re: plans for bitmap indexes?  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-hackers
On Tue, Oct 19, 2004 at 07:38:49PM -0300, Alvaro Herrera wrote:
> Huh, you are wrong.  At least btree does index null values, and one
> other index method does too.  The other two index methods don't.  What
> doesn't work is using an index with the IS NULL construct, because it's
> not an operator.  Maybe that can be fixed by some other means ... some
> parser magic perhaps.

Wow, that's news to me, and important to remember! Where is it
documented? I don't see it in the index chapter...

I think it would be very helpful to have a chapter that gives
information like this for experienced DBAs who are trying to learn
PostgreSQL and don't want to read through all the documentation but need
to know important differences in how PostgreSQL works that would be easy
to miss. Not indexing NULLs (ala Oracle), or not using an index for IS
NULL would certainly be examples. Things listed at
http://sql-info.de/postgresql/postgres-gotchas.html would also be likely
candidates.
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Should libpq set close-on-exec flag on its socket?
Next
From: Tom Lane
Date:
Subject: Re: Foreign key referential action timing