Remove a caveat from the "backup" documentation: pg_dump now does a

better job of handling dependencies between database objects.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 4a35a3f8a6468409c1411ae12f27a879510c4165..114d2ea588a98083853bff388f5fde2ae26a087e 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
 
 
  Backup and Restore
@@ -270,22 +270,6 @@ pg_dump -Fc dbname > 
   
    Caveats
 
-   
-    pg_dump (and by implication
-    pg_dumpall) has a few limitations which stem from
-    the difficulty of reconstructing certain information from the system
-    catalogs.
-   
-
-   
-    Specifically, the order in which 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.
-   
-
    
     For reasons of backward compatibility, pg_dump
     does not dump large objects by default.large