Going from a DB using SQL_ASCII to UNICODE

Поиск
Список
Период
Сортировка
От Dion Almaer
Тема Going from a DB using SQL_ASCII to UNICODE
Дата
Msg-id E1BFegz-00035r-2w@server1070.gisol.com
обсуждение исходный текст
Ответы Re: Going from a DB using SQL_ASCII to UNICODE  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Going from a DB using SQL_ASCII to UNICODE  (Frank Finner <postgresql@finner.de>)
Re: Going from a DB using SQL_ASCII to UNICODE  (CoL <col@mportal.hu>)
Re: Going from a DB using SQL_ASCII to UNICODE  (CoL <col@mportal.hu>)
Список pgsql-admin
Hi -

We are running PostgreSQL 7.1.4, and are finally upgrading... to 7.4.2.

While we do this upgrade, we also want to make create our DB as UNICODE (we
are having problems with SQL_ASCII where we get a bunch of ? marks).

When we try to import the data from a SQL_ASCII dumped db, into the new
UNICODE db, everything freaks out.
We get errors restoring from dumps that used COPY and with INSERT.

We also tried to use the 7.4 pg_dump to make sure that it wasn't a problem
with the old pg_dump.

The errors are:

- ERROR:  missing data for column "noiselevel"
- CONTEXT:  COPY messages, line 1: "4393  -1      1441    14147   0
2000-10-12 18:30:58-05  EJB Design Questions    \N      Hi,"
- FATAL:  invalid frontend message type 60
- ERROR:  invalid byte sequence for encoding "UNICODE": 0xe9616c

Anyway, if anyone has any recommendations on how to migrate from SQL_ASCII
to UNICODE, with the knowledge that we are going from 7.1 to 7.4 at the same
time.... You will be life-savers!

Cheers,

Dion


В списке pgsql-admin по дате отправления:

Предыдущее
От: "Bojan Belovic"
Дата:
Сообщение: Extremely high context switching
Следующее
От: "scott.marlowe"
Дата:
Сообщение: Re: Multiple disks