[Pkg-postgresql-public] Bug#810730: postgresql-common: should offer automatic cluster upgrading when installing a new major version

Felipe Sateler fsateler at debian.org
Mon Jan 11 17:00:38 UTC 2016


Package: postgresql-common
Version: 172
Severity: wishlist

Hi,

Today while installing 9.5, I got presented with the
postgresql-common/obsolete-major debconf prompt. I think it would be
great if it could automatically do the pg_updatecluster dance when
upgrading. At least for simple (default) setups (ie, only the
$version-main cluster).

Thanks.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages postgresql-common depends on:
ii  adduser                   3.113+nmu3
ii  debconf [debconf-2.0]     1.5.58
ii  init-system-helpers       1.24
ii  lsb-base                  9.20160110
ii  postgresql-client-common  172
ii  procps                    2:3.3.11-3
ii  ssl-cert                  1.0.37
ii  ucf                       3.0031

Versions of packages postgresql-common recommends:
ii  logrotate  3.8.7-2

postgresql-common suggests no packages.

-- debconf information:
  postgresql-common/catversion-bump:
  postgresql-common/ssl: true
* postgresql-common/obsolete-major:



More information about the Pkg-postgresql-public mailing list