Package: postgresql-common Version: 22 Severity: normal
Hi, I've just upgraded postgresql-8.0 and postgresql-common and found that postgresql-common is doing a "VACUUM FULL" on upgrade. This was a _rather_ unpleasant surprise since "VACUUM FULL" takes more than 2 hours on this machine. I think that causing such excessive database downtime for a package upgrade is unacceptable. And it is not even mentioned in changelog.Debian... Gabor Btw. pg_ctlcluster also prints a warning message: Use of uninitialized value in -r at /usr/bin/pg_ctlcluster line 112, <F> line 56. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) postgresql-common depends on no packages. Versions of packages postgresql-common recommends: ii openssl 0.9.7g-1 Secure Socket Layer (SSL) binary a -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
