<!--
-$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.32 2003/11/29 19:51:36 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.33 2004/01/11 05:46:58 neilc Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
</synopsis>
where <replaceable class="parameter">infile</replaceable> is what
you used as <replaceable class="parameter">outfile</replaceable>
- for the <command>pg_dump</> command. The database <replaceable
+ for the <application>pg_dump</> command. The database <replaceable
class="parameter">dbname</replaceable> will not be created by this
command, you must create it yourself from <literal>template0</> before executing
<application>psql</> (e.g., with <literal>createdb -T template0
</sect2>
<sect2 id="backup-dump-all">
- <title>Using <command>pg_dumpall</></title>
+ <title>Using <application>pg_dumpall</></title>
<para>
The above mechanism is cumbersome and inappropriate when backing
-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.191 2004/01/04 16:43:52 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.192 2004/01/11 05:46:58 neilc Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
</screen>
If you need to preserve OIDs (such as when using them as
foreign keys), then use the <option>-o</option> option when running
- <command>pg_dumpall</>.
+ <application>pg_dumpall</>.
</para>
<para>
- <command>pg_dumpall</command> does not
+ <application>pg_dumpall</application> does not
save large objects. Check
<![%standalone-include[the documentation]]>
<![%standalone-ignore[<xref linkend="backup-dump-caveats">]]>
</para>
<para>
- To make the backup, you can use the <command>pg_dumpall</command>
+ To make the backup, you can use the <application>pg_dumpall</application>
command from the version you are currently running. For best
- results, however, try to use the <command>pg_dumpall</command>
+ results, however, try to use the <application>pg_dumpall</application>
command from <productname>PostgreSQL</productname> &version;,
since this version contains bug fixes and improvements over older
versions. While this advice might seem idiosyncratic since you
<!--
-$PostgreSQL: pgsql/doc/src/sgml/perform.sgml,v 1.39 2003/12/14 00:10:32 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/perform.sgml,v 1.40 2004/01/11 05:46:58 neilc Exp $
-->
<chapter id="performance-tips">
<title>Populating a Database</title>
<para>
- One may need to do a large number of table insertions when first
- populating a database. Here are some tips and techniques for making that as
- efficient as possible.
+ One may need to insert a large amount of data when first populating
+ a database. This section contains some suggestions on how to make
+ this process as efficient as possible.
</para>
<sect2 id="disable-autocommit">
make sure the library does it when you want it done.)
If you allow each insertion to be committed separately,
<productname>PostgreSQL</productname> is doing a lot of work for each
- row added.
+ row that is added.
An additional benefit of doing all insertions in one transaction
is that if the insertion of one row were to fail then the
insertion of all rows inserted up to that point would be rolled
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/begin.sgml,v 1.28 2004/01/10 02:21:08 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/begin.sgml,v 1.29 2004/01/11 05:46:58 neilc Exp $
PostgreSQL documentation
-->
</variablelist>
<para>
- See under <xref linkend="sql-set-transaction"
- endterm="sql-set-transaction-title"> about the meaning of the
- other parameters.
+ Refer to <xref linkend="sql-set-transaction"
+ endterm="sql-set-transaction-title"> for information on the meaning
+ of the other parameters to this statement.
</para>
</refsect1>
<title>See Also</title>
<simplelist type="inline">
+ <member><xref linkend="sql-start-transaction" endterm="sql-start-transaction-title"></member>
<member><xref linkend="sql-commit" endterm="sql-commit-title"></member>
<member><xref linkend="sql-rollback" endterm="sql-rollback-title"></member>
</simplelist>
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_schema.sgml,v 1.10 2004/01/11 04:58:17 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_schema.sgml,v 1.11 2004/01/11 05:46:58 neilc Exp $
PostgreSQL documentation
-->
<title>Notes</title>
<para>
- To create a schema, the invoking user must have <literal>CREATE</>
- privilege for the current database. (Of course, superusers bypass
- this check.)
+ To create a schema, the invoking user must have the
+ <literal>CREATE</> privilege for the current database. (Of course,
+ superusers bypass this check.)
</para>
</refsect1>
SCHEMA</command> may appear in any order. The present
<productname>PostgreSQL</productname> implementation does not
handle all cases of forward references in subcommands; it may
- sometimes be necessary to reorder the subcommands to avoid forward
- references.
+ sometimes be necessary to reorder the subcommands in order to avoid
+ forward references.
</para>
<para>
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/start_transaction.sgml,v 1.10 2004/01/10 02:21:08 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/start_transaction.sgml,v 1.11 2004/01/11 05:46:58 neilc Exp $
PostgreSQL documentation
-->
<title>Parameters</title>
<para>
- See under <xref linkend="sql-set-transaction"
- endterm="sql-set-transaction-title"> about the meaning of the
- parameters.
+ Refer to <xref linkend="sql-set-transaction"
+ endterm="sql-set-transaction-title"> for information on the meaning
+ of the parameters to this statement.
</para>
</refsect1>
projects / postgresql / commitdiff