Message-ID: <3A41C989.6E83D1E@tm.ee>
Date: Thu, 21 Dec 2000 11:12:41 +0200
From: Hannu Krosing <hannu@tm.ee>
MIME-Version: 1.0
To: Oleg Bartunov <oleg@sai.msu.su>
CC: Tom Lane <tgl@sss.pgh.pa.us>, 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

Oleg Bartunov wrote:
> 
> We finished (cross fingers) our changes in GiST code for 7.0.3

Are tha patches for 7.0.3 already available ?

> 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 ?
> We have int4array contribution package which added index support for
> integer arrays 

what exactly does it mean ?

can i now query for an int4array which contains number 42 or just 
an int array that = '{1,2,3}' with index support ?

> 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.

Some samples will do fine for start ;)

> 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 ?

Great!

-------
Hannu