Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBILAW616673
	for <pgsql-hackers@postgresql.org>;
	Mon, 18 Dec 2000 16:10:32 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eBILAEC01645;
	Mon, 18 Dec 2000 16:10:14 -0500 (EST)
To: Oleg Bartunov <oleg@sai.msu.su>
cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Who is a maintainer of GiST code ? 
In-reply-to: <Pine.GSO.3.96.SK.1001218233711.7544B-100000@ra> 
References: <Pine.GSO.3.96.SK.1001218233711.7544B-100000@ra>
Comments: In-reply-to Oleg Bartunov <oleg@sai.msu.su>
	message dated "Mon, 18 Dec 2000 23:49:51 +0300"
Date: Mon, 18 Dec 2000 16:10:13 -0500
Message-ID: <1642.977173813@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200012/780
X-Sequence-Number: 2301

Oleg Bartunov <oleg@sai.msu.su> writes:
> We have a problem with
> handling NULL values in GiST. Any thought how NULL values
> are handle in Rtree.

AFAIR, none of the index access methods except btree handle NULLs at
all --- they just ignore NULL values and don't store them in the index.
Feel free to improve on that ;-).  The physical representation of index
tuples can handle NULLs, the problem is teaching the index logic where
they should go in the index.

			regards, tom lane