Package: postgresql-common Version: 208 Severity: normal As with every PostgreSQL major version upgrade, the README.Debian(.gz) from postgresql-common, symlinked in /usr/share/doc/postgresql-12/, suggests to drop the active (11) cluster, instead of the newly created empty (12) one.
│Then drop the default 11 cluster that was just created: │ │ pg_dropcluster 11 main --stop │ │And then upgrade the 9.6 cluster to the latest installed version (e. g. 11): │ │ pg_upgradecluster 9.6 main May I suggest to not symlink the README but instead generate it for each PostgreSQL server package, so that this doesn’t happen again? This must be the forth or so time I report this bug… -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages postgresql-common depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.73 ii lsb-base 11.1.0 ii perl 5.30.0-9 ii postgresql-client-common 208 ii procps 2:3.3.15-2 ii ssl-cert 1.0.39 ii ucf 3.0038+nmu1 Versions of packages postgresql-common recommends: ii e2fsprogs 1.45.4-1 ii logrotate 3.15.1-1 Versions of packages postgresql-common suggests: ii libjson-perl 4.02000-1 -- Configuration Files: /etc/sysctl.d/30-postgresql-shm.conf changed: kernel.shmmax=268435456 -- debconf information: postgresql-common/catversion-bump: postgresql-common/ssl: true * postgresql-common/obsolete-major:
