Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
eb06e6d1
Commit
eb06e6d1
authored
Aug 01, 2003
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve description of restoring pg_dumpall backups, per gripe from
Havard Eidnes.
parent
c4cf7fb8
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
8 deletions
+13
-8
doc/src/sgml/backup.sgml
doc/src/sgml/backup.sgml
+13
-8
No files found.
doc/src/sgml/backup.sgml
View file @
eb06e6d1
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.2
6 2003/03/24 14:32:50 petere
Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.2
7 2003/08/01 01:01:52 tgl
Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
...
...
@@ -163,16 +163,21 @@ pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>h
up an entire database cluster. For this reason the
<application>pg_dumpall</> program is provided.
<application>pg_dumpall</> backs up each database in a given
cluster
and also makes sure that the state of global
data such as
users and groups
is preserved
. The call sequence for
cluster
, and also preserves cluster-wide
data such as
users and groups. The call sequence for
<application>pg_dumpall</> is simply
<synopsis>
pg_dumpall > <replaceable>outfile</>
</synopsis>
The resulting dumps can be restored with <application>psql</> as
described above. But in this case it is definitely necessary that
you have database superuser access, as that is required to restore
the user and group information.
The resulting dump can be restored with <application>psql</>:
<synopsis>
psql template1 < <replaceable class="parameter">infile</replaceable>
</synopsis>
(Actually, you can specify any existing database name to start from,
but if you are reloading in an empty cluster then <literal>template1</>
is the only available choice.) It is always necessary to have
database superuser access when restoring a <application>pg_dumpall</>
dump, as that is required to restore the user and group information.
</para>
</sect2>
...
...
@@ -260,7 +265,7 @@ pg_dump -Fc <replaceable class="parameter">dbname</replaceable> > <replaceable c
<para>
<application>pg_dump</> (and by implication
<application>pg_dumpall</>) has a few limitations which stem from
the difficulty
to reconstruct
certain information from the system
the difficulty
of reconstructing
certain information from the system
catalogs.
</para>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment