From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Who is a maintainer of GiST code ? |
Date: | 2000-12-21 09:05:47 |
Message-ID: | 3A41C7EB.8134B661@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
Tom Lane wrote:
>
> Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> > seems rtree doesn't ignore NULL ?
>
> Hm, maybe not. There are explicit tests to ignore null inputs in hash
> indexes (hash/hash.c), and I'd just sort of assumed that rtree and gist
> do the same.
>
> FWIW, your example doesn't seem to provoke an error in current sources;
> but it does take quite a long time (far longer than building a btree
> index on 10000 nulls). That makes me think that indexing nulls in rtree
> might be a bad idea even if it works.
Or maybe just some optimisations done for large number of similar keys (
probabilistic page-splitting or some such ;) in btree are not done in
rtree ?
----------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-12-21 09:12:41 | Re: Who is a maintainer of GiST code ? |
Previous Message | Thomas Lockhart | 2000-12-21 06:00:57 | Re: Who is a maintainer of GiST code ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-12-21 09:12:41 | Re: Who is a maintainer of GiST code ? |
Previous Message | Thomas Lockhart | 2000-12-21 06:38:54 | Re: Future beta releases ... |