Index: doc/src/sgml/perform.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v
retrieving revision 1.73
diff -c -c -r1.73 perform.sgml
*** doc/src/sgml/perform.sgml	15 Jan 2010 09:18:59 -0000	1.73
--- doc/src/sgml/perform.sgml	26 Feb 2010 02:31:28 -0000
***************
*** 1027,1033 ****
         possibly discarding many hours of processing.  Depending on how
         interrelated the data is, that might seem preferable to manual cleanup,
         or not.  <command>COPY</> commands will run fastest if you use a single
!        transaction and have WAL archiving turned off.
        </para>
       </listitem>
       <listitem>
--- 1027,1036 ----
         possibly discarding many hours of processing.  Depending on how
         interrelated the data is, that might seem preferable to manual cleanup,
         or not.  <command>COPY</> commands will run fastest if you use a single
!        transaction and have WAL archiving turned off. 
!        <application>pg_restore</> also has a <option>--jobs</> option
!        which allows concurrent data loading and index creation, and has
!        the performance advantages of doing COPY in a single transaction.
        </para>
       </listitem>
       <listitem>