Make pg_dump's concurency capability more prominent.

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index b8c9694ea5b024c815d01e5c5681138a44d33fb9..79f30c771f9278e5358aa9a51ab4c228992b8d8f 100644 (file)
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
 
 
@@ -33,42 +33,47 @@ PostgreSQL documentation
   
 
   
-   pg_dump is a utility for saving a
-   PostgreSQL database into a script or an
-   archive file.  The script files are in plain-text format and
-   contain the SQL commands required to reconstruct the database to
-   the state it was in at the time it was saved.  To restore these
-   scripts, use .  They can be used to
-   reconstruct the database even on other machines and other
-   architectures, with some modifications even on other SQL database
-   products.
+   pg_dump is a utility for backing up a
+   PostgreSQL database. It makes consistent
+   backups even if the database is being used concurrently.
+   pg_dump does not block other users
+   accessing the database (readers or writers).
   
 
   
-   Furthermore, there are alternative archive file formats
-   that are meant to be used with  to
-   rebuild the database, and they also allow
-   pg_restore to be selective about what is
-   restored, or even to reorder the items prior to being restored. The
-   archive files are also designed to be portable across
+   Dumps can be output in script or archive file formats. The script
+   files are in plain-text format and contain the SQL commands required
+   to reconstruct the database to the state it was in at the time it was
+   saved. To restore these scripts, use . They
+   can be used to reconstruct the database even on other machines and
+   other architectures, with some modifications even on other SQL
+   database products.
+  
+
+  
+   The alternative archive file formats that are meant to be used with
+    to rebuild the database, and they also
+   allow pg_restore to be selective about
+   what is restored, or even to reorder the items prior to being
+   restored. The archive files are also designed to be portable across
    architectures.
   
 
   
    When used with one of the archive file formats and combined with
-   pg_restore, pg_dump provides a
-   flexible archival and 
+   pg_restore,
+   pg_dump provides a flexible archival and
    transfer mechanism. pg_dump can be used to
-   backup an entire database, then pg_restore can
-   be used to examine the archive and/or select which parts of the
-   database are to be restored.
-   The most flexible output file format is the custom
-   format (-Fc). It allows for selection and
-   reordering of all archived items, and is compressed by default. The
-   tar format (-Ft) is not
-   compressed and it is not possible to reorder data when loading, but
-   it is otherwise quite flexible; moreover, it can be manipulated with
-   other tools such as tar.
+   backup an entire database, then pg_restore
+   can be used to examine the archive and/or select which parts of the
+   database are to be restored. The most flexible output file format is
+   the custom format (-Fc). It allows
+   for selection and reordering of all archived items, and is compressed
+   by default. The tar format
+   (-Ft) is not compressed and it is not possible to
+   reorder data when loading, but it is otherwise quite flexible;
+   moreover, it can be manipulated with other tools such as
+   tar.
   
 
   
@@ -77,12 +82,6 @@ PostgreSQL documentation
    light of the limitations listed below.
   
 
-  
-   pg_dump makes consistent backups even if the
-   database is being used concurrently.  pg_dump
-   does not block other users accessing the database (readers or
-   writers).
-