Package: postgresql-common Version: 199.pgdg90+1 Followup-For: Bug #810615 Hallo,
i suspect the postgresql.auto.conf is not read at all by pg_upgradecluster howto reproduce 1. create a new cluster version 10 2. change a setting like the port or even a settings that would give an error if not correct, for example ssl=on in the standard conf with a custom non default certificate via alter system 3. upgrade the cluster 3.1 port will not be applied 3.2 will not start unless the postgresql.auto.conf is copied over manually (in case of the custom certificate) hth, Wim -- System Information: Debian Release: 9.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE:nl (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 199.pgdg90+1 ii procps 2:3.3.12-3+deb9u1 ii ssl-cert 1.0.39 ii ucf 3.0036 Versions of packages postgresql-common recommends: ii e2fsprogs 1.43.4-2 ii logrotate 3.11.0-0.1 Versions of packages postgresql-common suggests: pn libjson-perl <none> -- debconf information: postgresql-common/obsolete-major: postgresql-common/catversion-bump: postgresql-common/ssl: true
