11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.114 2009/08/07 20:54:31 alvherre Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.115 2010/02/19 03:50:03 momjian Exp $
33PostgreSQL documentation
44-->
55
@@ -25,6 +25,7 @@ PostgreSQL documentation
2525 <refsynopsisdiv>
2626 <cmdsynopsis>
2727 <command>pg_dump</command>
28+ <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
2829 <arg rep="repeat"><replaceable>option</replaceable></arg>
2930 <arg><replaceable>dbname</replaceable></arg>
3031 </cmdsynopsis>
@@ -51,7 +52,7 @@ PostgreSQL documentation
5152 saved. To restore from such a script, feed it to <xref
5253 linkend="app-psql">. Script files
5354 can be used to reconstruct the database even on other machines and
54- other architectures; with some modifications even on other SQL
55+ other architectures; with some modifications, even on other SQL
5556 database products.
5657 </para>
5758
@@ -530,7 +531,7 @@ PostgreSQL documentation
530531 than <command>COPY</command>). This will make restoration very slow;
531532 it is mainly useful for making dumps that can be loaded into
532533 non-<productname>PostgreSQL</productname> databases.
533- Also , since this option generates a separate command for each row,
534+ However , since this option generates a separate command for each row,
534535 an error in reloading a row causes only that row to be lost rather
535536 than the entire table contents.
536537 Note that
@@ -553,7 +554,7 @@ PostgreSQL documentation
553554 ...</literal>). This will make restoration very slow; it is mainly
554555 useful for making dumps that can be loaded into
555556 non-<productname>PostgreSQL</productname> databases.
556- Also , since this option generates a separate command for each row,
557+ However , since this option generates a separate command for each row,
557558 an error in reloading a row causes only that row to be lost rather
558559 than the entire table contents.
559560 </para>
@@ -636,7 +637,7 @@ PostgreSQL documentation
636637 <para>
637638 Output SQL-standard <command>SET SESSION AUTHORIZATION</> commands
638639 instead of <command>ALTER OWNER</> commands to determine object
639- ownership. This makes the dump more standards compatible, but
640+ ownership. This makes the dump more standards- compatible, but
640641 depending on the history of the objects in the dump, might not restore
641642 properly. Also, a dump using <command>SET SESSION AUTHORIZATION</>
642643 will certainly require superuser privileges to restore correctly,
@@ -834,7 +835,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
834835 does not contain the statistics used by the optimizer to make
835836 query planning decisions. Therefore, it is wise to run
836837 <command>ANALYZE</command> after restoring from a dump file
837- to ensure good performance; see <xref linkend="vacuum-for-statistics">
838+ to ensure optimal performance; see <xref linkend="vacuum-for-statistics">
838839 and <xref linkend="autovacuum"> for more information.
839840 The dump file also does not
840841 contain any <command>ALTER DATABASE ... SET</> commands;
0 commit comments