pgsql: Remove GIST concurrency limitations section.

Bruce Momjian wrote:

Remove GIST concurrency limitations section.

- <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.

-Neil

On Sun, 3 Jul 2005, Neil Conway wrote:

Bruce Momjian wrote:

Remove GIST concurrency limitations section.

- <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.

yes, this is the next step of our work on GiST. Call for support :)

-Neil

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

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

- <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

Christopher Kings-Lynne <chriskl@familyhealth.com.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

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

Oleg Bartunov wrote:

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

Added to TODO:

* Allow GIST indexes to create certain complex index types, like digital
trees (see Aoki)

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073