Package: postgresql-common Version: 278 Severity: normal X-Debbugs-Cc: [email protected]
pg_dump/pg_restore is very slow. It might take days if upgrading relatively small cluster of 200Gb. (I got one from persoinal using of matrix-synapse for several years, so even a single person can have cluster that big now) My suggestion is either completely make `-m upgrade` a new default, or add new method `auto` that will use either `dump` of `upgrade` depending on cluster size. pg_upgrade is safe and fast, and is widely used in production, and I see no reason for not using it all the time by default. And since `pg_upgradecluster` is started while upgrading the system, I would also suggest to add a menu that asks for upgrade method. May be And since I both perl developer and deal with PostgreSQL core code on regular basis I can provide patches for these functionality, if Debian PostgreSQL Maintainers approve the idea. -- System Information: Debian Release: 13.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.48+deb13-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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.152 ii debconf [debconf-2.0] 1.5.91 ii init-system-helpers 1.69~deb13u1 ii libjson-perl 4.10000-1 ii lsb-base 11.6 ii perl 5.40.1-6 ii postgresql-client-common 278 ii postgresql-common-dev 278 ii ssl-cert 1.1.3 ii sysvinit-utils [lsb-base] 3.14-4 ii ucf 3.0052 Versions of packages postgresql-common recommends: ii e2fsprogs 1.47.2-3+b3 ii logrotate 3.22.0-1 postgresql-common suggests no packages. -- debconf information excluded
