Package: postgresql-common
Version: 223.pgdg100+1
Severity: normal
pg_createcluster has an option to include this line in postgresql.conf:
include_dir = 'conf.d'
pg_upgradecluster doesn't copy the files in conf.d to the new cluster
I needed to copy the files manually after the upgrade and restart the
cluster.
this is similar / related to bug #960789
-- System Information:
Debian Release: 10.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages postgresql-common depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.71
ii lsb-base 10.2019051400
ii perl 5.28.1-6+deb10u1
ii postgresql-client-common 223.pgdg100+1
ii ssl-cert 1.0.39
ii ucf 3.0038+nmu1
Versions of packages postgresql-common recommends:
ii e2fsprogs 1.44.5-1+deb10u3
ii logrotate 3.14.0-4
Versions of packages postgresql-common suggests:
pn libjson-perl <none>
-- Configuration Files:
/etc/apt/apt.conf.d/01autoremove-postgresql changed:
// NO NOT EDIT!
// File maintained by /usr/share/postgresql-common/pg_updateaptconfig.
//
// Mark all PostgreSQL packages as NeverAutoRemove for which PostgreSQL
// clusters exist. This is especially important when the "postgresql" meta
// package changes its dependencies to a new version, which might otherwise
// trigger the old postgresql-NN package to be automatically removed, rendering
// the old database cluster inaccessible.
APT
{
NeverAutoRemove
{
"^postgresql.*-13";
};
};
-- debconf information:
postgresql-common/catversion-bump:
postgresql-common/obsolete-major:
postgresql-common/ssl: true
