8000 Make pg_dump's concurency capability more prominent. · postgrespro/postgres@76fd678 · GitHub
[go: up one dir, main page]
Skip to content

Commit 76fd678

Browse files
bmomjianbmomjian
committed
Make pg_dump's concurency capability more prominent.
1 parent 31845dd commit 76fd678

File tree

1 file changed

+33
-34
lines changed

1 file changed

+33
-34
lines changed

‎doc/src/sgml/ref/pg_dump.sgml

Lines changed: 33 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.60 2003/03/25 16:15:42 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.61 2003/04/17 15:34:37 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -33,42 +33,47 @@ PostgreSQL documentation
3333
</title>
3434

3535
<para>
36-
<application>pg_dump</application> is a utility for saving a
37-
<productname>PostgreSQL</productname> database into a script or an
38-
archive file. The script files are in plain-text format and
39-
contain the SQL commands required to reconstruct the database to
40-
the state it was in at the time it was saved. To restore these
41-
scripts, use <xref linkend="app-psql">. They can be used to
42-
reconstruct the database even on other machines and other
43-
architectures, with some modifications even on other SQL database
44-
products.
36+
<application>pg_dump</application> is a utility for backing up a
37+
<productname>PostgreSQL</productname> database. It makes consistent
38+
backups even if the database is being used concurrently.
39+
<application>pg_dump</application> does not block other users
40+
accessing the database (readers or writers).
4541
</para>
4642

4743
<para>
48-
Furthermore, there are alternative archive file formats
49-
that are meant to be used with <xref linkend="app-pgrestore"> to
50-
rebuild the database, and they also allow
51-
<application>pg_restore</application> to be selective about what is
52-
restored, or even to reorder the items prior to being restored. The
53-
archive files are also designed to be portable across
44+
Dumps can be output in script or archive file formats. The script
45+
files are in plain-text format and contain the SQL commands required
46+
to reconstruct the database to the state it was in at the time it was
47+
saved. To restore these scripts, use <xref li 10000 nkend="app-psql">. They
48+
can be used to reconstruct the database even on other machines and
49+
other architectures, with some modifications even on other SQL
50+
database products.
51+
</para>
52+
53+
<para>
54+
The alternative archive file formats that are meant to be used with
55+
<xref linkend="app-pgrestore"> to rebuild the database, and they also
56+
allow <application>pg_restore</application> to be selective about
57+
what is restored, or even to reorder the items prior to being
58+
restored. The archive files are also designed to be portable across
5459
architectures.
5560
</para>
5661

5762
<para>
5863
When used with one of the archive file formats and combined with
59-
<application>pg_restore</application>, <application>pg_dump</application> provides a
60-
flexible archival and
64+
<application>pg_restore</application>,
65+
<application>pg_dump</application> provides a flexible archival and
6166
transfer mechanism. <application>pg_dump</application> can be used to
62-
backup an entire database, then <application>pg_restore</application> can
63-
be used to examine the archive and/or select which parts of the
64-
database are to be restored.
65-
The most flexible output file format is the <quote>custom</quote>
66-
format (<option>-Fc</option>). It allows for selection and
67-
reordering of all archived items, and is compressed by default. The
68-
<application>tar</application> format (<option>-Ft</option>) is not
69-
compressed and it is not possible to reorder data when loading, but
70-
it is otherwise quite flexible; moreover, it can be manipulated with
71-
other tools such as <command>tar</command>.
67+
backup an entire database, then <application>pg_restore</application>
68+
can be used to examine the archive and/or select which parts of the
69+
database are to be restored. The most flexible output file format is
70+
the <quote>custom</quote> format (<option>-Fc</option>). It allows
71+
for selection and reordering of all archived items, and is compressed
72+
by default. The <application>tar</application> format
73+
(<option>-Ft</option>) is not compressed and it is not possible to
74+
reorder data when loading, but it is otherwise quite flexible;
75+
moreover, it can be manipulated with other tools such as
76+
<command>tar</command>.
7277
</para>
7378

7479
<para>
@@ -77,12 +82,6 @@ PostgreSQL documentation
7782
light of the limitations listed below.
7883
</para>
7984

80-
<para>
81-
<application>pg_dump</application> makes consistent backups even if the
82-
database is being used concurrently. <application>pg_dump</application>
83-
does not block other users accessing the database (readers or
84-
writers).
85-
</para>
8685
</refsect1>
8786

8887
<refsect1 id="pg-dump-options">

0 commit comments

Comments
 (0)
0