| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | 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 00:29:11 |
| Message-ID: | 42C882D7.1000101@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-07-04 02:02:01 | pgsql: Bruce, please apply this additional patch, that fixes the |
| Previous Message | User Andrewd | 2005-07-03 23:33:34 | pgbuildfarm - client-code: add comments to sample config making it |