Re: pgsql: Remove GIST concurrency limitations section.

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Remove GIST concurrency limitations section.
Date: 2005-07-04 12:32:53
Message-ID: 200507041232.j64CWr517576@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Oleg Bartunov wrote:
> On Mon, 4 Jul 2005, Christopher Kings-Lynne wrote:
>
> >> - <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.
>
> ok, it's sort of TODO

Added to TODO:

* Allow GIST indexes to create certain complex index types, like digital
trees (see Aoki)

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2005-07-04 14:12:46 pgsql: Fix date_trunct for December dates that are in the next year,
Previous Message Bruce Momjian 2005-07-04 12:32:39 pgsql: Update > * Allow GIST indexes to create certain complex index