mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-12 15:39:35 +08:00
Make pg_dump's concurency capability more prominent.
This commit is contained in:
parent
31845dd363
commit
76fd678c06
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.60 2003/03/25 16:15:42 petere Exp $
|
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.61 2003/04/17 15:34:37 momjian Exp $
|
||||||
PostgreSQL documentation
|
PostgreSQL documentation
|
||||||
-->
|
-->
|
||||||
|
|
||||||
@ -33,42 +33,47 @@ PostgreSQL documentation
|
|||||||
</title>
|
</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
<application>pg_dump</application> is a utility for saving a
|
<application>pg_dump</application> is a utility for backing up a
|
||||||
<productname>PostgreSQL</productname> database into a script or an
|
<productname>PostgreSQL</productname> database. It makes consistent
|
||||||
archive file. The script files are in plain-text format and
|
backups even if the database is being used concurrently.
|
||||||
contain the SQL commands required to reconstruct the database to
|
<application>pg_dump</application> does not block other users
|
||||||
the state it was in at the time it was saved. To restore these
|
accessing the database (readers or writers).
|
||||||
scripts, use <xref linkend="app-psql">. They can be used to
|
|
||||||
reconstruct the database even on other machines and other
|
|
||||||
architectures, with some modifications even on other SQL database
|
|
||||||
products.
|
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Furthermore, there are alternative archive file formats
|
Dumps can be output in script or archive file formats. The script
|
||||||
that are meant to be used with <xref linkend="app-pgrestore"> to
|
files are in plain-text format and contain the SQL commands required
|
||||||
rebuild the database, and they also allow
|
to reconstruct the database to the state it was in at the time it was
|
||||||
<application>pg_restore</application> to be selective about what is
|
saved. To restore these scripts, use <xref linkend="app-psql">. They
|
||||||
restored, or even to reorder the items prior to being restored. The
|
can be used to reconstruct the database even on other machines and
|
||||||
archive files are also designed to be portable across
|
other architectures, with some modifications even on other SQL
|
||||||
|
database products.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
The alternative archive file formats that are meant to be used with
|
||||||
|
<xref linkend="app-pgrestore"> to rebuild the database, and they also
|
||||||
|
allow <application>pg_restore</application> 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.
|
architectures.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
When used with one of the archive file formats and combined with
|
When used with one of the archive file formats and combined with
|
||||||
<application>pg_restore</application>, <application>pg_dump</application> provides a
|
<application>pg_restore</application>,
|
||||||
flexible archival and
|
<application>pg_dump</application> provides a flexible archival and
|
||||||
transfer mechanism. <application>pg_dump</application> can be used to
|
transfer mechanism. <application>pg_dump</application> can be used to
|
||||||
backup an entire database, then <application>pg_restore</application> can
|
backup an entire database, then <application>pg_restore</application>
|
||||||
be used to examine the archive and/or select which parts of the
|
can be used to examine the archive and/or select which parts of the
|
||||||
database are to be restored.
|
database are to be restored. The most flexible output file format is
|
||||||
The most flexible output file format is the <quote>custom</quote>
|
the <quote>custom</quote> format (<option>-Fc</option>). It allows
|
||||||
format (<option>-Fc</option>). It allows for selection and
|
for selection and reordering of all archived items, and is compressed
|
||||||
reordering of all archived items, and is compressed by default. The
|
by default. The <application>tar</application> format
|
||||||
<application>tar</application> format (<option>-Ft</option>) is not
|
(<option>-Ft</option>) is not compressed and it is not possible to
|
||||||
compressed and it is not possible to reorder data when loading, but
|
reorder data when loading, but it is otherwise quite flexible;
|
||||||
it is otherwise quite flexible; moreover, it can be manipulated with
|
moreover, it can be manipulated with other tools such as
|
||||||
other tools such as <command>tar</command>.
|
<command>tar</command>.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
@ -77,12 +82,6 @@ PostgreSQL documentation
|
|||||||
light of the limitations listed below.
|
light of the limitations listed below.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
|
||||||
<application>pg_dump</application> makes consistent backups even if the
|
|
||||||
database is being used concurrently. <application>pg_dump</application>
|
|
||||||
does not block other users accessing the database (readers or
|
|
||||||
writers).
|
|
||||||
</para>
|
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
<refsect1 id="pg-dump-options">
|
<refsect1 id="pg-dump-options">
|
||||||
|
Loading…
Reference in New Issue
Block a user