Your message dated Sun, 4 Apr 2010 20:13:42 +0200
with message-id <[email protected]>
and subject line Re: Bug#539585: postgresql-8.3: wrong encoding when migrating 
cluster
has caused the Debian Bug report #539585,
regarding postgresql-8.3: wrong encoding when migrating cluster
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.)


-- 
539585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539585
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-8.3
Version: 8.3.7-0lenny1
Severity: normal

My locale is UTF8.
Migrating from 8.1 to 8.3 the new cluster was LATIN9.
This screwed up postfix because it works with latin1 and it is not possible to 
convert.
So to make it work i had to dump the entire cluster, delete it, recreate with 
the utf8 encoding as it was supposed to be from the beginning and then load it 
again.
So i guess the new clusters should be automatically created with the system 
encoding by default which is not, since i had to manually specify it (and the 
manpage said it was not a good idea to specify the encoding and don't let the 
locale do its job).


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages postgresql-8.3 depends on:
ii  libc6           2.7-18                   GNU C Library: Shared libraries
ii  libcomerr2      1.41.3-1                 common error description library
ii  libkrb53        1.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries
ii  libldap-2.4-2   2.4.11-1                 OpenLDAP libraries
ii  libpam0g        1.0.1-5+lenny1           Pluggable Authentication Modules l
ii  libpq5          8.3.7-0lenny1            PostgreSQL C client library
ii  libssl0.9.8     0.9.8g-15+lenny1         SSL shared libraries
ii  libxml2         2.6.32.dfsg-5            GNOME XML library
ii  locales         2.7-18                   GNU C Library: National Language (
ii  postgresql-clie 8.3.7-0lenny1            front-end programs for PostgreSQL 
ii  postgresql-comm 94lenny1                 PostgreSQL database-cluster manage
ii  ssl-cert        1.0.23                   simple debconf wrapper for OpenSSL
ii  tzdata          2009g-0lenny1            time zone and daylight-saving time

postgresql-8.3 recommends no packages.

Versions of packages postgresql-8.3 suggests:
pn  oidentd | ident-server        <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Hello,

the database is on a working system, after _so many months_ I don't really 
have any way to get back the old configuration.

> @euro is latin9, so the old and new cluster had the same locale then.
> So it seems it works as designed?

I can tell you that the authentication using pg was working, and after the 
upgrade it wasn't working anymore because pg8.3 couldn't convert from latin9 
to latin1 (required by pam).
So i can presume the encoding wasn't latin9 when i was using pg8.1, or there 
was a way to convert from latin9 to latin1 that was later removed.

For sure the authentication was working before the upgrade and wasn't working 
after. And i had to dump and create again into utf8 to make it work again.

Are you sure it was designed like this?

Regards
-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
                -- Galileo Galilei


--- End Message ---

Reply via email to