From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hannu Krosing <hannu@tm.ee>
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: Mon, 18 Dec 2000 19:25:38 -0500
Message-ID: <2483.977185538@sss.pgh.pa.us> (raw)
In-Reply-To: <3A3EA5F2.DF22E9E6@tm.ee>
References: <Pine.GSO.3.96.SK.1001218233711.7544B-100000@ra>
<1642.977173813@sss.pgh.pa.us>
<3A3EA5F2.DF22E9E6@tm.ee>
Hannu Krosing <hannu@tm.ee> writes:
> and I can't see why btree stores them (as it seems to do judging by the
> index file size) - at least it does not use it for searching for "IS
> NULL"
That's another thing that needs improvement ;-). Seems to me it should
be able to do that.
The reason why btree *has* to be able to deal with null entries is to
cope with multi-column indexes; you don't want it refusing to index a
row at all just because some of the columns are null. The others don't
currently handle multi-column indexes, so they're not really forced
to deal with that issue.
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: tgl@sss.pgh.pa.us, hannu@tm.ee, 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: <2483.977185538@sss.pgh.pa.us>
* 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