11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.19 2005/06/20 14:53:32 tgl Exp $
33-->
44
55<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 $
186186 <para>
187187 The current implementation of <acronym>GiST</acronym> within
188188 <productname>PostgreSQL</productname> has some major limitations:
189- <acronym>GiST</acronym> access is not concurrent; the
189+ <acronym>GiST</acronym>index access is not concurrent, and the
190190 <acronym>GiST</acronym> interface doesn't allow the development of certain
191- data types, such as digital trees (see papers by Aoki et al); and there
192- is not yet any support for write-ahead logging of updates in
193- <acronym>GiST</acronym> indexes.
191+ data types, such as digital trees (see papers by Aoki et al).
194192 </para>
195193
196194 <para>
@@ -199,12 +197,6 @@ $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $
199197 <productname>PostgreSQL</productname> implementation.
200198 </para>
201199
202- <para>
203- The lack of write-ahead logging is just a small matter of programming,
204- but since it isn't done yet, a crash could render a <acronym>GiST</acronym>
205- index inconsistent, forcing a <command>REINDEX</command>.
206- </para>
207-
208200</sect1>
209201
210202<sect1 id="examples">