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

Commit387a3e4

Browse files
committed
pg_upgrade: force timeline 1 in the new cluster
Previously, this prevented promoted standby servers from being upgradedbecause of a missing WAL history file. (Timeline 1 doesn't need ahistory file, and we don't copy WAL files anyway.)Report by Christian Echerer(?), Alexey KlyukinBackpatch through 9.0
1 parent31f5d3f commit387a3e4

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎contrib/pg_upgrade/pg_upgrade.c‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -658,8 +658,9 @@ copy_clog_xlog_xid(void)
658658
/* now reset the wal archives in the new cluster */
659659
prep_status("Resetting WAL archives");
660660
exec_prog(UTILITY_LOG_FILE,NULL, true,
661-
"\"%s/pg_resetxlog\" -l %s \"%s\"",new_cluster.bindir,
662-
old_cluster.controldata.nextxlogfile,
661+
/* use timeline 1 to match controldata and no WAL history file */
662+
"\"%s/pg_resetxlog\" -l 00000001%s \"%s\"",new_cluster.bindir,
663+
old_cluster.controldata.nextxlogfile+8,
663664
new_cluster.pgdata);
664665
check_ok();
665666
}

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp