| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Jim Nasby <decibel(at)decibel(dot)org> |
| Cc: | Marcus Engene <mengpg(at)engene(dot)se>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: IN clause |
| Date: | 2006-11-28 14:01:55 |
| Message-ID: | 20061128140155.GA29938@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 27, 2006 at 05:24:31PM -0600, Jim Nasby wrote:
> In any case, like Oracle, PostgreSQL does not index NULL values (at
> least not in btree).
Actually, PostgreSQL does store NULL values in an index, otherwise you
could never use them for full index scans (think multicolumn indexes).
You can't use the index for IS NULL tests, although patches exist for
that.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John D. Burger | 2006-11-28 14:42:38 | Re: NULLs ;-) |
| Previous Message | Jakub Ouhrabka | 2006-11-28 13:40:10 | Re: vacuum: out of memory error |