Your message dated Mon, 31 Mar 2008 11:47:03 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#472930: fixed in postgresql-common 87 has caused the Debian Bug report #472930, regarding pg_upgradecluster fails because database ENCODING does not match server's LC_CTYPE to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472930 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: postgresql-common Version: 86 Severity: important I am testing an upgrade procedure from 8.1 to 8.3 and I get this error: duo:~# LC_ALL=C LANG=C pg_upgradecluster -v 8.3 8.1 main Creating new cluster (configuration: /etc/postgresql/8.3/main, data: /var/lib/postgresql/8.3/main)... Moving configuration file /var/lib/postgresql/8.3/main/postgresql.conf to /etc/postgresql/8.3/main... Moving configuration file /var/lib/postgresql/8.3/main/pg_hba.conf to /etc/postgresql/8.3/main... Moving configuration file /var/lib/postgresql/8.3/main/pg_ident.conf to /etc/postgresql/8.3/main... Configuring postgresql.conf to use port 5432... Disabling connections to the old cluster during upgrade... Disabling connections to the new cluster during upgrade... Re-enabling connections to the old cluster... Re-enabling connections to the new cluster... Creating globals... Fixing hardcoded library paths for stored procedures... Upgrading database lixpergroupware... pg_restore: [archiver (db)] Error while PROCESSING TOC: pg_restore: [archiver (db)] Error from TOC entry 3030; 1262 16401 DATABASE lixpergroupware postgres pg_restore: [archiver (db)] could not execute query: ERROR: encoding LATIN1 does not match server's locale it_IT.UTF-8 DETAIL: The server's LC_CTYPE setting requires encoding UTF8. Command was: CREATE DATABASE lixpergroupware WITH TEMPLATE = template0 ENCODING = 'LATIN1'; pg_restore: [archiver (db)] could not execute query: ERROR: database "lixpergroupware" does not exist Command was: ALTER DATABASE lixpergroupware OWNER TO postgres; pg_restore: [archiver (db)] could not reconnect to database: FATAL: database "lixpergroupware" does not exist Error during cluster dumping, removing new cluster The packages installed are: ii libpq4 8.1.11-0etch1 PostgreSQL C client library ii libpq5 8.3.1-1 PostgreSQL C client library ii postgresql-8.1 8.1.11-0etch1 object-relational SQL database, version 8.1 server ii postgresql 8.3.1-1 object-relational SQL database (latest version) ii postgresql-8.3 8.3.1-1 object-relational SQL database, version 8.3 server ii postgresql-client-8.1 8.1.11-0etch1 front-end programs for PostgreSQL 8.1 ii postgresql-client-8.3 8.3.1-1 front-end programs for PostgreSQL 8.3 ii postgresql-client-common 86 manager for multiple PostgreSQL client versions ii postgresql-common 86 PostgreSQL database-cluster manager ii postgresql-contrib-8.3 8.3.1-1 additional facilities for PostgreSQL This machine is a debian etch plus postgresql and postgresql-common from unstable (recompiled). Bye, Giuseppe
--- End Message ---
--- Begin Message ---Source: postgresql-common Source-Version: 87 We believe that the bug you reported is fixed in the latest version of postgresql-common, which is due to be installed in the Debian FTP archive: postgresql-client-common_87_all.deb to pool/main/p/postgresql-common/postgresql-client-common_87_all.deb postgresql-common_87.dsc to pool/main/p/postgresql-common/postgresql-common_87.dsc postgresql-common_87.tar.gz to pool/main/p/postgresql-common/postgresql-common_87.tar.gz postgresql-common_87_all.deb to pool/main/p/postgresql-common/postgresql-common_87_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt <[EMAIL PROTECTED]> (supplier of updated postgresql-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 31 Mar 2008 11:32:39 +0200 Source: postgresql-common Binary: postgresql-common postgresql-client-common Architecture: source all Version: 87 Distribution: unstable Urgency: medium Maintainer: Martin Pitt <[EMAIL PROTECTED]> Changed-By: Martin Pitt <[EMAIL PROTECTED]> Description: postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - PostgreSQL database-cluster manager Closes: 472930 473405 Changes: postgresql-common (87) unstable; urgency=medium . * Urgency medium since #472930 is an important bug fix. * debian/init.d-functions: If there are no clusters, exit with 4 (LSB-code for "unknown status") instead of 0 (which means "service is running", but it is debatable and confusing whether all clusters are running if there are none at all). (LP: #203966) * Update Spanish debconf translations, thanks Javier Fernández-Sanguino Peña. (Closes: #473405) * t/060_obsolete_confparams.t: Run upgrades under default_transaction_read_only=on. t/040_upgrade.t still uses the default "off", so both cases get tested. This replicates the problem report from Karsten Hilbert. * pg_upgradecluster: Work with default_transaction_read_only=on. * debian/autovacuum.conf, architecture.html: Point out that this file is only relevant for PostgreSQL versions earlier than 8.1. Thanks to Ross Boylan for pointing this out. * Add t/051_inconsistent_encoding_upgrade.t: Check that upgrades from pre-8.3 to 8.3 succeed and have correct encodings if the old DB had a database whose encoding did not match the server locale. This reproduces #472930. * pg_upgradecluster: Fix handling of database encodings on upgrade, since 8.3 now forces DB encodings and server locale to match: - With C locale, keep encoding of DBs on upgrade, just as in previous versions. (C is compatible with all encodings, and causes lots of string functions not to work correctly, but people still use it deliberately.) - With other locales, create the target DB manually with a compatible encoding, and call pg_restore in a way to not create the target DB and automatically convert encoding. - Closes: #472930, LP: #207779 Files: bea6888ba8e5963033a702d6604f4a81 599 misc optional postgresql-common_87.dsc b0fddfcd7b126f20c6aeb8624cffbbaa 106527 misc optional postgresql-common_87.tar.gz 116bd096f07d3b20c5cddcf85fbd7232 107128 misc optional postgresql-common_87_all.deb 77a0a75fee34d3bc76c754b83f152866 44904 misc optional postgresql-client-common_87_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH8MqtDecnbV4Fd/IRAjL4AKCuG38rU7uwnzbQyvMmPVv/XMJiDQCdGxll T4WPfYH8lCWMdb2+z88BV70= =sse5 -----END PGP SIGNATURE-----
--- End Message ---
