Re: pgsql: Remove GIST concurrency limitations section. - Mailing list pgsql-committers

From Christopher Kings-Lynne
Subject Re: pgsql: Remove GIST concurrency limitations section.
Date
Msg-id 42C882D7.1000101@familyhealth.com.au
Whole thread Raw
In response to Re: pgsql: Remove GIST concurrency limitations section.  (Neil Conway <neilc@samurai.com>)
Responses Re: pgsql: Remove GIST concurrency limitations section.  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql: Remove GIST concurrency limitations section.  (Oleg Bartunov <oleg@sai.msu.su>)
List pgsql-committers
> - <para>
> -  The current implementation of <acronym>GiST</acronym> within
> -  <productname>PostgreSQL</productname> has some major limitations:
> -  <acronym>GiST</acronym> index access is not concurrent, and the
> -  <acronym>GiST</acronym> interface doesn't allow the development of
> certain
> -  data types, such as digital trees (see papers by Aoki et al).
> - </para>
>
> AFAIK the GiST modifications suggested Aoki have not yet been
> implemented, so this should not have been removed.

I thought that was an extremely vague limitation and could easily be
removed...  It's like having a limitations section on btrees and have
mentioning in passing that it can't do full text indexing or something.

Chris

pgsql-committers by date:

Previous
From: andrewd@pgfoundry.org (User Andrewd)
Date:
Subject: pgbuildfarm - client-code: add comments to sample config making it
Next
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Bruce, please apply this additional patch, that fixes the