[Pkg-postgresql-public] Bug#876281: postgresql-common: pg_upgradecluster should support --no-start or similar

[Magnus Hagander]

Package: postgresql-common
Version: 184.pgdg90+1
Severity: important

Currently, pg_upgradecluster unconditionally starts the cluster when the upgrade is complete. This
makes it impossible to use the hardlink-to-slave method for rapidly upgrading a multi node cluster
that's documented on https://www.postgresql.org/docs/9.6/static/pgupgrade.html.

I suggest adding a --no-start option to it that will leave the new cluster stopped, making it possible
to do the rest of the work elsewhere.

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postgresql-common depends on:
ii  adduser                   3.115
ii  debconf [debconf-2.0]     1.5.61
ii  init-system-helpers       1.48
ii  lsb-base                  9.20161125
ii  postgresql-client-common  184.pgdg90+1
ii  procps                    2:3.3.12-3
ii  ssl-cert                  1.0.39
ii  ucf                       3.0036

Versions of packages postgresql-common recommends:
ii  logrotate  3.11.0-0.1

Versions of packages postgresql-common suggests:
ii  libjson-perl  2.90-1

-- debconf information excluded