| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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 02:12:57 |
| Message-ID: | 2553.1120443177@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> 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.
Yeah, I agree. It'd be appropriate to mention the Aoki paper in TODO,
but we don't normally document "stuff we'd like to do someday" as
serious limitations.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2005-07-04 02:56:02 | pgsql: Fix build break for out of tree (vpath) builds, induced by recent |
| Previous Message | Bruce Momjian | 2005-07-04 02:02:01 | pgsql: Bruce, please apply this additional patch, that fixes the |