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

diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml
index 9577a0768a92aee3197a269506d243b3e47d0444..f2a583393031e22ec505c2fbe5ef5c7212786636 100644 (file)
--- a/doc/src/sgml/gist.sgml
+++ b/doc/src/sgml/gist.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -186,11 +186,9 @@ $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $
  
   The current implementation of GiST within
   PostgreSQL has some major limitations:
-  GiST access is not concurrent; the
+  GiST index access is not concurrent, and the
   GiST 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
-  GiST indexes.
+  data types, such as digital trees (see papers by Aoki et al).
  
 
  
@@ -199,12 +197,6 @@ $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $
   PostgreSQL implementation.
  
 
- 
-  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 GiST
-  index inconsistent, forcing a REINDEX.
- 
-