Re: pgsql: Remove GIST concurrency limitations section.

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

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

>
> Chris
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2005-07-04 04:51:53 pgsql: Arrange for the postmaster (and standalone backends, initdb, etc)
Previous Message Bruce Momjian 2005-07-04 04:17:01 pgsql: Reverse this patch: