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

Commitcc2e457

Browse files
committed
doc: "Latest checkpoint location" will not match in pg_upgrade
Mention that "Latest checkpoint location" will not match in pg_upgradeif the standby server is still running during the upgrade, which ispossible. "Match" text first appeared in PG 9.5.Reported-by: Paul BonaudDiscussion:https://postgr.es/m/c7268794-edb4-1772-3bfd-04c54585c24e@trainline.comBackpatch-through: 9.5
1 parentdcb2efd commitcc2e457

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -326,7 +326,8 @@ NET STOP postgresql-&majorversion;
326326
against the old primary and standby clusters. Verify that the
327327
<quote>Latest checkpoint location</quote> values match in all clusters.
328328
(There will be a mismatch if old standby servers were shut down
329-
before the old primary.) Also, change <varname>wal_level</varname> to
329+
before the old primary or if the old standby servers are still running.)
330+
Also, change <varname>wal_level</varname> to
330331
<literal>replica</literal> in the <filename>postgresql.conf</filename> file on the
331332
new primary cluster.
332333
</para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp