pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Who is a maintainer of GiST code ?
Date: Thu, 21 Dec 2000 11:05:47 +0200
Message-ID: <3A41C7EB.8134B661@tm.ee> (raw)
References: <Pine.GSO.3.96.SK.1001219222315.19999H-100000@ra>
	<11222.977342421@sss.pgh.pa.us>

Tom Lane wrote:
> 
> Oleg Bartunov <oleg@sai.msu.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



view thread (19+ messages)  latest in thread

Message-ID: <3A41C7EB.8134B661@tm.ee>
Permalink:  ../3A41C7EB.8134B661@tm.ee/
Also on:    postgresql.org/message-id/3A41C7EB.8134B661@tm.ee

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: hannu@tm.ee, tgl@sss.pgh.pa.us, oleg@sai.msu.su, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: Who is a maintainer of GiST code ?
  In-Reply-To: <3A41C7EB.8134B661@tm.ee>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox