Index: doc/src/sgml/backup.sgml
===================================================================
RCS file: /cvsroot/pgsql-server/doc/src/sgml/backup.sgml,v
retrieving revision 2.24
diff -c -c -r2.24 backup.sgml
*** doc/src/sgml/backup.sgml 11 Nov 2002 20:14:02 -0000 2.24
--- doc/src/sgml/backup.sgml 17 Mar 2003 23:58:37 -0000
***************
*** 126,131 ****
--- 126,138 ----
+ Once restored, it is wise to run ANALYZE> on each
+ database so the optimizer has useful statistics. You
+ can also run vacuumdb -a -z> to ANALYZE> all
+ databases.
+
+
+
The ability of pg_dump> and psql> to
write to or read from pipes makes it possible to dump a database
directly from one server to another, for example
Index: doc/src/sgml/ref/pg_dump.sgml
===================================================================
RCS file: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_dump.sgml,v
retrieving revision 1.56
diff -c -c -r1.56 pg_dump.sgml
*** doc/src/sgml/ref/pg_dump.sgml 13 Feb 2003 04:54:15 -0000 1.56
--- doc/src/sgml/ref/pg_dump.sgml 17 Mar 2003 23:58:38 -0000
***************
*** 650,655 ****
--- 650,660 ----
+
+ Once restored, it is wise to run ANALYZE> on each
+ restored object so the optimizer has useful statistics.
+
+
pg_dump has a few limitations:
***************
*** 682,687 ****
--- 687,698 ----
other output formats is not limited, except possibly by the
operating system.
+
+
+ Once restored, it is wise to run ANALYZE> on each
+ restored object so the optimizer has useful statistics.
+
+
Index: doc/src/sgml/ref/pg_dumpall.sgml
===================================================================
RCS file: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_dumpall.sgml,v
retrieving revision 1.36
diff -c -c -r1.36 pg_dumpall.sgml
*** doc/src/sgml/ref/pg_dumpall.sgml 6 Jan 2003 18:53:24 -0000 1.36
--- doc/src/sgml/ref/pg_dumpall.sgml 17 Mar 2003 23:58:38 -0000
***************
*** 258,267 ****
pg_dumpall will need to connect several
times to the PostgreSQL server. If password
authentication is configured, it will ask for a password each time. In
! that case it would be convenient to set up a password file.
- But where is that password file documented?
--- 258,274 ----
pg_dumpall will need to connect several
times to the PostgreSQL server. If password
authentication is configured, it will ask for a password each time. In
! that case it would be convenient to set up a .pgpass>
! password file.
!
!
!
! Once restored, it is wise to run ANALYZE> on each
! database so the optimizer has useful statistics. You
! can also run vacuumdb -a -z> to ANALYZE> all
! databases.
Index: doc/src/sgml/ref/pg_restore.sgml
===================================================================
RCS file: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_restore.sgml,v
retrieving revision 1.35
diff -c -c -r1.35 pg_restore.sgml
*** doc/src/sgml/ref/pg_restore.sgml 19 Jan 2003 00:13:31 -0000 1.35
--- doc/src/sgml/ref/pg_restore.sgml 17 Mar 2003 23:58:47 -0000
***************
*** 589,594 ****
--- 589,600 ----
See also the documentation for details on
limitations of pg_dump.
+
+
+ Once restored, it is wise to run ANALYZE> on each
+ restored object so the optimizer has useful statistics.
+
+