From: Bruce Momjian Date: Thu, 9 May 2013 20:05:26 +0000 (-0400) Subject: pg_upgrade docs: give tips on automation X-Git-Tag: REL9_3_BETA2~110 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=df9d764186cf6082376e25fe04050ad39462312d;p=postgresql 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. --- diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index 12f86f77b4..d676d286ab 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 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.