Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitdf9d764

Browse files
committed
pg_upgrade docs: give tips on automation
Document that post-upgrade steps are likely to be the same for allclusters with the same DDL/schemas; this should help automatedupgrades.
1 parent284e28f commitdf9d764

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)

[8]ページ先頭

©2009-2025 Movatter.jp