database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-24 10:47:04 +03:00
Code

Remove statement that GiST indexes aren't WAL-logged.

Browse Source
This commit is contained in:
Tom Lane 2005-06-20 14:53:32 +00:00
parent f0e7f9e30b
commit 3f6a094be1
1 changed files with 3 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/gist.sgml
View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $
$PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.19 2005/06/20 14:53:32 tgl Exp $
-->
<chapter id="GiST">
@ -186,11 +186,9 @@ $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $
<para>
The current implementation of <acronym>GiST</acronym> within
<productname>PostgreSQL</productname> has some major limitations:
<acronym>GiST</acronym> access is not concurrent; the
<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); and there
is not yet any support for write-ahead logging of updates in
<acronym>GiST</acronym> indexes.
data types, such as digital trees (see papers by Aoki et al).
</para>
<para>
@ -199,12 +197,6 @@ $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $
<productname>PostgreSQL</productname> implementation.
</para>
<para>
The lack of write-ahead logging is just a small matter of programming,
but since it isn't done yet, a crash could render a <acronym>GiST</acronym>
index inconsistent, forcing a <command>REINDEX</command>.
</para>
</sect1>
<sect1 id="examples">