Skip to content

Commit df9d764

Browse files
committed
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.
1 parent 284e28f commit df9d764

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

doc/src/sgml/pgupgrade.sgml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -518,7 +518,11 @@ psql --username postgres --file script.sql postgres
518518
All failure, rebuild, and reindex cases will be reported by
519519
<application>pg_upgrade</> if they affect your installation;
520520
post-upgrade scripts to rebuild tables and indexes will be
521-
generated automatically.
521+
generated automatically. If you are trying to automate the upgrade
522+
of many clusters, you should find that clusters with identical database
523+
schemas require the same post-upgrade steps for all cluster upgrades;
524+
this is because the post-upgrade steps are based on the database
525+
schemas, and not user data.
522526
</para>
523527

524528
<para>

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy