Package: postgresql-common Version: 281.pgdg120+1 Followup-For: Bug #960789
Dear Maintainer, I try to upgrade DB postgresql 17 to 18. So I install postgresql-18 (from PostgreSQL repo) and then run "pg_upgradecluster -m link 17 main"... It fails on checking wal_level of the new cluster because wal_level is expected to be logical but it is actually replica. Reason: I have redefined default settings in the extra config file located in the /etc/postgresql/17/main/conf.d/custom.conf. It permits more quick review of settings and migration over servers. So I have wal_level=logical defined there, but not in the /etc/postgresql/17/main/postgresql.conf. If I redefine it in the /etc/postgresql/17/main/postgresql.conf then pg_upgradecluster succeed. pg_upgradecluster should copy conf.d/* files to the new cluster directory. Best regards, Sergey Belyashov -- System Information: Debian Release: 12.12 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/8 CPU threads) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postgresql-common depends on: ii adduser 3.134 ii debconf [debconf-2.0] 1.5.82 ii init-system-helpers 1.65.2+deb12u1 ii libjson-perl 4.10000-1 ii lsb-base 11.6 ii perl 5.36.0-7+deb12u3 ii postgresql-client-common 281.pgdg120+1 ii postgresql-common-dev 281.pgdg120+1 ii ssl-cert 1.1.2 ii sysvinit-utils [lsb-base] 3.06-4 ii ucf 3.0043+nmu1+deb12u1 Versions of packages postgresql-common recommends: ii e2fsprogs 1.47.0-2+b2 ii logrotate 3.21.0-1 postgresql-common suggests no packages. -- debconf information: postgresql-common/obsolete-major: postgresql-common/ssl: true postgresql-common/catversion-bump:
