diff options
| author | Neil Conway <neilc@samurai.com> | 2005-05-17 00:59:30 +0000 |
|---|---|---|
| committer | Neil Conway <neilc@samurai.com> | 2005-05-17 00:59:30 +0000 |
| commit | eda6dd32d15fe85bfddf6caf32d1a861c4fa5957 (patch) | |
| tree | 4571423ee6d25e00fc02d12ba30a55220acabcf0 /doc/src | |
| parent | 818bfda1e27b6f5441c9fc6a5bcd9048e8003553 (diff) | |
GiST improvements:
- make sure we always invoke user-supplied GiST methods in a short-lived
memory context. This means the backend isn't exposed to any memory leaks
that be in those methods (in fact, it is probably a net loss for most
GiST methods to bother manually freeing memory now). This also means
we can do away with a lot of ugly manual memory management in the
GiST code itself.
- keep the current page of a GiST index scan pinned, rather than doing a
ReadBuffer() for each tuple produced by the scan. Since ReadBuffer() is
expensive, this is a perf. win
- implement dead tuple killing for GiST indexes (which is easy to do, now
that we keep a pin on the current scan page). Now all the builtin indexes
implement dead tuple killing.
- cleanup a lot of ugly code in GiST
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/gist.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml index e5c96d7e542..9577a0768a9 100644 --- a/doc/src/sgml/gist.sgml +++ b/doc/src/sgml/gist.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.17 2005/04/09 03:52:43 momjian Exp $ +$PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.18 2005/05/17 00:59:30 neilc Exp $ --> <chapter id="GiST"> @@ -202,7 +202,7 @@ $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.17 2005/04/09 03:52:43 momjian Exp <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 REINDEX. + index inconsistent, forcing a <command>REINDEX</command>. </para> </sect1> |