diff options
| author | Bruce Momjian <bruce@momjian.us> | 2013-05-09 16:05:26 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2013-05-09 16:05:26 -0400 |
| commit | df9d764186cf6082376e25fe04050ad39462312d (patch) | |
| tree | ba691a89297dce13e5fb01fd7c5e7d1ce344a639 | |
| parent | 284e28f2280a8f69014df689ae5e2843eebd7c59 (diff) | |
| download | postgresql-df9d764186cf6082376e25fe04050ad39462312d.tar.gz postgresql-df9d764186cf6082376e25fe04050ad39462312d.zip | |
pg_upgrade docs: give tips on automation
Document that post-upgrade steps are likely to be the same for all
clusters with the same DDL/schemas; this should help automated
upgrades.
| -rw-r--r-- | doc/src/sgml/pgupgrade.sgml | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index 12f86f77b40..d676d286ab2 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -518,7 +518,11 @@ psql --username postgres --file script.sql postgres All failure, rebuild, and reindex cases will be reported by <application>pg_upgrade</> if they affect your installation; post-upgrade scripts to rebuild tables and indexes will be - generated automatically. + generated automatically. If you are trying to automate the upgrade + of many clusters, you should find that clusters with identical database + schemas require the same post-upgrade steps for all cluster upgrades; + this is because the post-upgrade steps are based on the database + schemas, and not user data. </para> <para> |