Package: postgresql-client-common
Version: 223
Severity: normal
When accessing a remote cluster pg_wrapper always select the newest
version of pg_dump. This, combined with pg_restore on a local cluster
results in an error when multiple clusters with different PostgreSQL
versions are available on the local machine.
For example, if the local machine has both PostgreSQL 11 and 12
installed, the following command will fail:
pg_dump -Fc -h $REMOTE_HOST -p $REMOTE_PORT remote_db \
| pg_restore -Fc -d pg11_db
because pg_wrapper will use pg_dump version 12 and pipe the result
into pg_restore version 11 (that does not support a dump generated
with pg_dump version 12).
A possible solution is to always use the last version of pg_restore
(it is backward compatible so there should be no issues).
-- System Information:
Debian Release: bullseye/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-4-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages postgresql-client-common depends on:
ii netbase 6.2
Versions of packages postgresql-client-common recommends:
ii libreadline8 8.1~rc3-1
postgresql-client-common suggests no packages.
-- no debconf information
