diff options
| author | Bruce Momjian <bruce@momjian.us> | 2017-06-20 13:20:02 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2017-06-20 13:20:10 -0400 |
| commit | b710248dd3f90c46bd4208e6bf1290048b9d76cd (patch) | |
| tree | bb8e23e5b82f34205611cd8e1a33be28655da4c5 /src/backend/access/gist/gistbuild.c | |
| parent | a69dfe5f40f77d586e8d4d9ecfc39d81612c7dda (diff) | |
| download | postgresql-b710248dd3f90c46bd4208e6bf1290048b9d76cd.tar.gz | |
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/20170620171844.GC24975@momjian.us
Backpatch-through: 9.2
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions