Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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

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

In response to


pgsql-committers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group