Re: dump_all/restore times?

Here is an applied patch that suggests increasing sort_mem during
restore.  I though of putting it near the database restore section or in
the manual, but is seemed more centralized to put it near the actual
parameter.


---------------------------------------------------------------------------

Kaarel wrote:
>
> >>I was thinking the very same thing. If it is a must to always bump up
> >>sort_mem before running restore why can't the restore utility do it?
> >>Take a portion of the currently available memory or ask a user
> >>interactively etc.
> >>
> >>
> >
> >This would need to be a command line option, because there may be systems
> >on which bumping up sort_mem should not be done, for reasons unrelated to
> >performance during the restore, and the restore may not always be done
> >interactively.
> >
> >
> If this can not be done then at least the sort_mem thing should be
> mentioned in Chapter 9. Backup and Restore in the PostgreSQL
> Administrator's Guide.
> http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html#sortmem too
> only slightly mentiones data dumps as opposed to "before running the
> restore" suggested by Tom.
>
> Kaarel
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
>                http://archives.postgresql.org
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
Index: doc/src/sgml/runtime.sgml
===================================================================
RCS file: /cvsroot/pgsql-server/doc/src/sgml/runtime.sgml,v
retrieving revision 1.194
diff -c -c -r1.194 runtime.sgml
*** doc/src/sgml/runtime.sgml    22 Jul 2003 20:29:13 -0000    1.194
--- doc/src/sgml/runtime.sgml    23 Jul 2003 20:13:53 -0000
***************
*** 887,893 ****
          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.
         </para>
        </listitem>
       </varlistentry>
--- 887,895 ----
          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.  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>