Index: doc/src/sgml/ref/pg_dump.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v
retrieving revision 1.103
diff -c -c -r1.103 pg_dump.sgml
*** doc/src/sgml/ref/pg_dump.sgml	20 Jul 2008 18:43:30 -0000	1.103
--- doc/src/sgml/ref/pg_dump.sgml	21 Aug 2008 22:11:32 -0000
***************
*** 754,775 ****
    </para>
  
    <para>
!    <application>pg_dump</application> has a few limitations:
! 
!    <itemizedlist>
!     <listitem>
!      <para>
!       When a data-only dump is chosen and the option
!       <option>--disable-triggers</> is used,
!       <application>pg_dump</application> emits commands to disable
!       triggers on user tables before inserting the data and commands
!       to re-enable them after the data has been inserted.  If the
!       restore is stopped in the middle, the system catalogs might be
!       left in the wrong state.
!      </para>
!     </listitem>
! 
!    </itemizedlist>
    </para>
  
    <para>
--- 754,766 ----
    </para>
  
    <para>
!    <application>pg_dump</application> has a limitation; when a
!    data-only dump is chosen and the option <option>--disable-triggers</>
!    is used, <application>pg_dump</application> emits commands
!    to disable triggers on user tables before inserting the data
!    and commands to re-enable them after the data has been
!    inserted.  If the restore is stopped in the middle, the system
!    catalogs might be left in the wrong state.
    </para>
  
    <para>
***************
*** 782,792 ****
    </para>
  
    <para>
!    The dump file produced by <application>pg_dump</application> does
!    not contain the statistics used by the optimizer to make query
!    planning decisions.  Therefore, it is wise to run
!    <command>ANALYZE</command> after restoring from a dump file to
!    ensure good performance.
    </para>
  
    <para>
--- 773,786 ----
    </para>
  
    <para>
!    The dump file produced by <application>pg_dump</application>
!    does not contain the statistics used by the optimizer to make
!    query planning decisions.  Therefore, it is wise to run
!    <command>ANALYZE</command> after restoring from a dump file
!    to ensure good performance.  The dump file also does not
!    contain any <command>ALTER DATABASE ... SET</> commands;
!    these settings are dumped by <xref linkend="app-pg-dumpall">,
!    along with database users and other installation-wide settings.
    </para>
  
    <para>
