[COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal - Mailing list pgsql-committers

From Bruce Momjian
Subject [COMMITTERS] pgsql: pg_upgrade: start/stop new server after pg_resetwal
Date
Msg-id E1dNMp6-00022M-1y@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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

Branch
------
REL9_4_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/a0e8548811f6a4a47fe747fea72edcc3c4bf3f27

Modified Files
--------------
contrib/pg_upgrade/check.c      | 19 +++++++++++--------
contrib/pg_upgrade/pg_upgrade.c |  2 +-
contrib/pg_upgrade/pg_upgrade.h |  2 +-
3 files changed, 13 insertions(+), 10 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Don't downcase entries within shared_preload_libraries et al.
Next
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Upgrade documentation connected with shared_preload_librarieset