Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
afcc6fbb
Commit
afcc6fbb
authored
21 years ago
by
Neil Conway
Browse files
Options
Downloads
Patches
Plain Diff
Remove a caveat from the "backup" documentation: pg_dump now does a
better job of handling dependencies between database objects.
parent
0128c17c
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/backup.sgml
+1
-17
1 addition, 17 deletions
doc/src/sgml/backup.sgml
with
1 addition
and
17 deletions
doc/src/sgml/backup.sgml
+
1
−
17
View file @
afcc6fbb
<!--
<!--
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.3
6
2004/02/17
09:07:16
neilc Exp $
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.3
7
2004/02/17
23:56:07
neilc Exp $
-->
-->
<chapter id="backup">
<chapter id="backup">
<title>Backup and Restore</title>
<title>Backup and Restore</title>
...
@@ -270,22 +270,6 @@ pg_dump -Fc <replaceable class="parameter">dbname</replaceable> > <replaceable c
...
@@ -270,22 +270,6 @@ pg_dump -Fc <replaceable class="parameter">dbname</replaceable> > <replaceable c
<sect2 id="backup-dump-caveats">
<sect2 id="backup-dump-caveats">
<title>Caveats</title>
<title>Caveats</title>
<para>
<application>pg_dump</> (and by implication
<application>pg_dumpall</>) has a few limitations which stem from
the difficulty of reconstructing certain information from the system
catalogs.
</para>
<para>
Specifically, the order in which <application>pg_dump</> writes
the objects is not very sophisticated. This can lead to problems
for example when functions are used as column default values. The
only answer is to manually reorder the dump. If you created
circular dependencies in your schema then you will have more work
to do.
</para>
<para>
<para>
For reasons of backward compatibility, <application>pg_dump</>
For reasons of backward compatibility, <application>pg_dump</>
does not dump large objects by default.<indexterm><primary>large
does not dump large objects by default.<indexterm><primary>large
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment