pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Hannu Krosing <hannu@tm.ee>
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 06:00:57 +0000
Message-ID: <3A419C99.934EEFA4@alumni.caltech.edu> (raw)
References: <Pine.GSO.3.96.SK.1001220231854.19999R-100000@ra>

> 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



view thread (19+ messages)  latest in thread

Message-ID: <3A419C99.934EEFA4@alumni.caltech.edu>
Permalink:  ../3A419C99.934EEFA4@alumni.caltech.edu/
Also on:    postgresql.org/message-id/3A419C99.934EEFA4@alumni.caltech.edu

 · 

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: lockhart@alumni.caltech.edu, oleg@sai.msu.su, tgl@sss.pgh.pa.us, hannu@tm.ee, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: Who is a maintainer of GiST code ?
  In-Reply-To: <3A419C99.934EEFA4@alumni.caltech.edu>

* 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