From 0221bc97cf8722ef5c8107da4e5d9e25aa8a93af Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 23 Jul 2003 20:30:35 +0000
Subject: [PATCH] Mention increasing sort_mem during a restore.

---
 doc/src/sgml/runtime.sgml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index bab8d2751d..1f28e21559 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.194 2003/07/22 20:29:13 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.195 2003/07/23 20:30:35 momjian Exp $
 -->
 
 <Chapter Id="runtime">
@@ -887,7 +887,9 @@ SET ENABLE_SEQSCAN TO OFF;
         times the value of <varname>SORT_MEM</varname>. Sort operations are used
         by <literal>ORDER BY</>, merge joins, and <command>CREATE INDEX</>.
         Hash tables are used in hash joins, hash-based aggregation, and
-        hash-based processing of <literal>IN</> subqueries.
+        hash-based processing of <literal>IN</> subqueries.  Because 
+        <command>CREATE INDEX</> is used when restoring a database, it might
+        be good to temporary increase this value during a restore.
        </para>
       </listitem>
      </varlistentry>