Re: pgsql: Remove GIST concurrency limitations section.

Поиск
Список
Период
Сортировка
От Oleg Bartunov
Тема Re: pgsql: Remove GIST concurrency limitations section.
Дата
Msg-id Pine.GSO.4.63.0507040830040.8797@ra.sai.msu.su
обсуждение исходный текст
Ответ на Re: pgsql: Remove GIST concurrency limitations section.  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Ответы Re: pgsql: Remove GIST concurrency limitations section.  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список 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@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

В списке pgsql-committers по дате отправления:

Предыдущее
От: momjian@svr1.postgresql.org (Bruce Momjian)
Дата:
Сообщение: pgsql: Reverse this patch:
Следующее
От: tgl@svr1.postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Arrange for the postmaster (and standalone backends, initdb, etc)