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

Commit64bbe10

Browse files
committed
docs: clarify pg_upgrade's recovery behavior
The previous paragraph trying to explain --check, --link, and no --linkmodes and the various points of failure was too complex. Instead, usebullet lists and sublists.Reported-by: Daniel GustafssonDiscussion:https://postgr.es/m/qtqiv7hI87s_Xvz5ZXHCaH-1-_AZGpIDJowzlRjF3-AbCr3RhSNydM_JCuJ8DE4WZozrtxhIWmyYTbv0syKyfGB6cYMQitp9yN-NZMm-oAo=@yesql.seBackpatch-through: 9.4
1 parent1a75c1d commit64bbe10

File tree

1 file changed

+36
-16
lines changed

1 file changed

+36
-16
lines changed

‎doc/src/sgml/ref/pgupgrade.sgml

Lines changed: 36 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -678,32 +678,52 @@ psql --username=postgres --file=script.sql postgres
678678
<itemizedlist>
679679
<listitem>
680680
<para>
681-
If you ran <command>pg_upgrade</command>
682-
with <option>--check</option>, no modifications were made to the old
683-
cluster and you can re-use it anytime.
681+
If the <option>--check</option> option was used, the old cluster
682+
was unmodified; it can be restarted.
684683
</para>
685684
</listitem>
686685

687686
<listitem>
688687
<para>
689-
If you ran <command>pg_upgrade</command>
690-
with <option>--link</option>, the data files are shared between the
691-
old and new cluster. If you started the new cluster, the new
692-
server has written to those shared files and it is unsafe to
693-
use the old cluster.
688+
If the <option>--link</option> option was <emphasis>not</emphasis>
689+
used, the old cluster was unmodified; it can be restarted.
694690
</para>
695691
</listitem>
696692

697693
<listitem>
698694
<para>
699-
If you ran <command>pg_upgrade</command> <emphasis>without</emphasis>
700-
<option>--link</option> or did not start the new server, the
701-
old cluster was not modified except that, if linking
702-
started, a <literal>.old</literal> suffix was appended to
703-
<filename>$PGDATA/global/pg_control</filename>. To reuse the old
704-
cluster, possibly remove the <filename>.old</filename> suffix from
705-
<filename>$PGDATA/global/pg_control</filename>; you can then restart the
706-
old cluster.
695+
If the <option>--link</option> option was used, the data
696+
files might be shared between the old and new cluster:
697+
698+
<itemizedlist>
699+
<listitem>
700+
<para>
701+
If <command>pg_upgrade</command> aborted before linking started,
702+
the old cluster was unmodified; it can be restarted.
703+
</para>
704+
</listitem>
705+
706+
<listitem>
707+
<para>
708+
If you did <emphasis>not</emphasis> start the new cluster, the old
709+
cluster was unmodified except that, when linking started, a
710+
<literal>.old</literal> suffix was appended to
711+
<filename>$PGDATA/global/pg_control</filename>. To reuse the old
712+
cluster, remove the <filename>.old</filename> suffix from
713+
<filename>$PGDATA/global/pg_control</filename>; you can then restart
714+
the old cluster.
715+
</para>
716+
</listitem>
717+
718+
<listitem>
719+
<para>
720+
If you did start the new cluster, it has written to shared files
721+
and it is unsafe to use the old cluster. The old cluster will
722+
need to be restored from backup in this case.
723+
</para>
724+
</listitem>
725+
726+
</itemizedlist>
707727
</para>
708728
</listitem>
709729
</itemizedlist>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp