Package: postgresql-client-common Version: 113 Severity: normal
Whilst the reference here to something in passing is "very minor", for me it was not :) Our 8.3 postgresql.conf contained the following: # data_dir = '/path/to/somewhere' data_dir = '/var/lib/postgresql/8.3/main' pg_upgradecluster changed this to the following: data_dir = '/var/lib/postgresql/8.4/main' data_dir = '/var/lib/postgresql/8.3/main' Which then meant it got confused; when it tried to stop the new cluster it looks like the old one stopped and then it died when trying to stop the old cluster. I wasn't sure how far pg_upgradecluster had got, so resorted to reverting back to clean 8.3 cluster, removing the commented out data_dir line from our 8.3 config, and then pg_upgradecluster worked okay. It looks like PgCommon.pm (in set_conf_value()) will take the first commented or uncommented line containing the config key and replace it with an uncommented line, which would lead to the behaviour seen. I think it would be preferable for it change an uncommented line over a commented line if one is present, as this caused quite a bit of head-scratching late last night. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash postgresql-client-common depends on no packages. Versions of packages postgresql-client-common recommends: ii lsb-release 3.2-23.2squeeze1 Linux Standard Base version report postgresql-client-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
