From: Bruce Momjian Date: Tue, 18 Mar 2003 00:02:11 +0000 (+0000) Subject: Add mention of ANALYZE after object restore. X-Git-Tag: REL7_4_BETA1~922 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=29c18bca5021e09b8d9d99e6ff5e0ed27cc96f61;p=thirdparty%2Fpostgresql.git Add mention of ANALYZE after object restore. --- diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 327990e5584..a58945f1ef0 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,5 +1,5 @@ Backup and Restore @@ -125,6 +125,13 @@ psql dbname < + + 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 diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index d8ae789fbe2..3b35c0da698 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -650,6 +650,11 @@ CREATE DATABASE foo WITH TEMPLATE template0; + + 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,6 +687,12 @@ CREATE DATABASE foo WITH TEMPLATE template0; 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. + + diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index 64cea1f4a63..b584bb447ab 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -1,5 +1,5 @@ @@ -258,10 +258,17 @@ PostgreSQL documentation 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. + 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. - But where is that password file documented? diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index be76f55a36c..427cbd45514 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -1,4 +1,4 @@ - + @@ -589,6 +589,12 @@ CREATE DATABASE foo WITH TEMPLATE = template0; 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. + +