Skip site navigation (1) Skip section navigation (2)

Going from a DB using SQL_ASCII to UNICODE

From: "Dion Almaer" <dion(at)almaer(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Cc: "'Lloyd Benson'" <lloyd(at)middleware-company(dot)com>,"Eric Preston" <eric(at)middleware-company(dot)com>
Subject: Going from a DB using SQL_ASCII to UNICODE
Date: 2004-04-19 19:44:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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!




pgsql-admin by date

Next:From: scott.marloweDate: 2004-04-19 19:59:44
Subject: Re: Multiple disks
Previous:From: scott.marloweDate: 2004-04-19 15:58:37
Subject: Re: PGfs Codebase? even old version????bb at wv dot com

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group