encoding problem - Mailing list pgsql-admin

From Alexey A. Britchko
Subject encoding problem
Date
Msg-id 14060489484.20030325110759@roaddep.ru
Whole thread Raw
Responses Re: encoding problem
List pgsql-admin
Hi there

How did upgrade from pgsql 6.x to pgsql 7.x:
1. Dumped database
2. ./configure --enable-locale --enable-multibyte=WIN; make; make
install;
3. Killed postmaster daemon
3. rm -rf /usr/local/pgsql/data; mkdir /usr/local/pgsql/data; chown
postgres /usr/local/pgsql/data;
4. /usr/local/pgsql/bin/initdb -E WIN -D /usr/local/pgsql/data
5. Started postmaster daemon
6. Restored database from dbdump file.

What i've got now:

$ /usr/local/pgsql/bin/psql -l
        List of databases
   Name    |  Owner   | Encoding
-----------+----------+-----------
 dcl       | raven    | SQL_ASCII
 dragons   | raven    | SQL_ASCII
 postgres  | postgres | SQL_ASCII
 template0 | postgres | WIN
 template1 | postgres | WIN
 test      | postgres | SQL_ASCII
(6 rows)

The default encoding for 4 of databases is SQL_ASCII. Well, that's OK.
The database encoding is shure to be described in the dump file. And
it seems to be restored correctly.

But now when I make selections, I get data in the SQL_ASCII (a think
so) encoding instead of WIN (WIN1251). Before PostgreSQL upgrade
everything were working correctly.

The questions:
1. What happens with the database encoding when I do pg_dumpall ?
2. How can I permanently switch database encoding without
database re-initialization? If I can't, how can I do that with DB
re-initialization?

--
Best regards,
 Alexey                          mailto:beholder@roaddep.ru


pgsql-admin by date:

Previous
From: "Devi Munandar"
Date:
Subject: stable phppgadmin version
Next
From: "Tamir Halperin"
Date:
Subject: Zope and ZPsycopgDA almost working...