Message-ID: <3A419C99.934EEFA4@alumni.caltech.edu>
Date: Thu, 21 Dec 2000 06:00:57 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
Organization: Yes
MIME-Version: 1.0
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Hannu Krosing <hannu@tm.ee>,
	Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Who is a maintainer of GiST code ?
References: <Pine.GSO.3.96.SK.1001220231854.19999R-100000@ra>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> We finished (cross fingers) our changes in GiST code for 7.0.3
> and in next 2 days we plan to send patches for upcoming 7.1 release.
> Isn't this too late ? What else we need to submit ?

Not too late, especially if it is fixing bugs. And even if not, anything
we can do to encourage active development and use of GiST is worth the
effort imho. I'll guess that unless we are talking about some extreme,
far-reaching changes in the backend others will agree.

> We have int4array contribution package which added index support for
> integer arrays and it's probably should come to contrib directory.
> We got about 3 orders of magnitude speedup using RD-Tree.
> Probably we need to add regression test for GiST.
> We have following fixes for GiST (7.0.3):
> 1. indices now store on disk in  compressed form - was decompressed which
>    causes broken index when using compression function
>    (now compression of indices is really works)
> 2. NULLs now don't broken index
> 3. added support for keys with variable length - was fixed-length
> Patches and contribution package could be prepared in several days,
> documentation with some benchmarks and blurbs require more time.
> We plan to use these last changes to speedup our full-text-search
> ( killer application ) and write article to popularize GiST+Postgres.
> Any thoughts ?

Go go go !!! :)

                       - Thomas