[Pkg-postgresql-public] Bug#876282: postgresql-common: pg_upgradecluster checks for pg_restore parameters when using pg_upgrade
Magnus Hagander
magnus at hagander.net
Wed Sep 20 13:16:11 UTC 2017
Package: postgresql-common
Version: 184.pgdg90+1
Severity: normal
pg_upgradecluster has a check for no-data-for-failed-tables whereby it checks pg_restore
compatibility as soon as there are any upgrade scripts available.
This check should only run when using dump/restore mode, not when using pg_upgrade mode, I believe.
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (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 184.pgdg90+1
ii procps 2:3.3.12-3
ii ssl-cert 1.0.39
ii ucf 3.0036
Versions of packages postgresql-common recommends:
ii logrotate 3.11.0-0.1
Versions of packages postgresql-common suggests:
ii libjson-perl 2.90-1
-- debconf information excluded
More information about the Pkg-postgresql-public
mailing list