diff options
| author | Bruce Momjian | 2017-06-20 17:20:02 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2017-06-20 17:20:10 +0000 |
| commit | b710248dd3f90c46bd4208e6bf1290048b9d76cd (patch) | |
| tree | bb8e23e5b82f34205611cd8e1a33be28655da4c5 /src/bin/pg_upgrade/pg_upgrade.h | |
| parent | a69dfe5f40f77d586e8d4d9ecfc39d81612c7dda (diff) | |
pg_upgrade: start/stop new server after pg_resetwal
When commit 0f33a719fdbb5d8c43839ea0d2c90cd03e2af2d2 removed the
instructions to start/stop the new cluster before running rsync, it was
now possible for pg_resetwal/pg_resetxlog to leave the final WAL record
at wal_level=minimum, preventing upgraded standby servers from
reconnecting.
This patch fixes that by having pg_upgrade unconditionally start/stop
the new cluster after pg_resetwal/pg_resetxlog has run.
Backpatch through 9.2 since, though the instructions were added in PG
9.5, they worked all the way back to 9.2.
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.2
Diffstat (limited to 'src/bin/pg_upgrade/pg_upgrade.h')
| -rw-r--r-- | src/bin/pg_upgrade/pg_upgrade.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/pg_upgrade/pg_upgrade.h b/src/bin/pg_upgrade/pg_upgrade.h index 8fbf8acd7eb..e3a577a7823 100644 --- a/src/bin/pg_upgrade/pg_upgrade.h +++ b/src/bin/pg_upgrade/pg_upgrade.h @@ -332,7 +332,7 @@ void output_check_banner(bool live_check); void check_and_dump_old_cluster(bool live_check); void check_new_cluster(void); void report_clusters_compatible(void); -void issue_warnings(void); +void issue_warnings_and_set_wal_level(void); void output_completion_banner(char *analyze_script_file_name, char *deletion_script_file_name); void check_cluster_versions(void); |