mirror of
https://github.com/postgres/postgres.git
synced 2025-04-27 22:56:53 +03:00
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.
This commit is contained in:
parent
284e28f228
commit
df9d764186
@ -518,7 +518,11 @@ psql --username postgres --file script.sql postgres
|
|||||||
All failure, rebuild, and reindex cases will be reported by
|
All failure, rebuild, and reindex cases will be reported by
|
||||||
<application>pg_upgrade</> if they affect your installation;
|
<application>pg_upgrade</> if they affect your installation;
|
||||||
post-upgrade scripts to rebuild tables and indexes will be
|
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>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user