From: | jesse(dot)waters(at)gmail(dot)com |
---|---|
To: | "Michael Glaesemann" <grzm(at)seespotcode(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: UTF8 frustrations |
Date: | 2007-09-05 19:28:59 |
Message-ID: | 8b3a63b10709051228o7f34f6b6k6746bc30421d7bcd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks all for the quick replies.
Here is the latest issue, to verify that the pg_dump works, I'm going
to do dump and restore on the same host/cluster.
Source:
DB_source:
Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
psql 8.2.4
Destination:
same machine different db name
echo $LANG
en_US.UTF-8
SET client_encoding = 'UTF8';
Command used:
pg_dump -Fc srcdb > db.dump
pg_restore -d devdb db.dump
Results, same error. Now I'm really concerned.
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 1625; 0 16680 TABLE
DATA logs watersj
pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence
for encoding "UTF8": 0xdf69
HINT: This error can also happen if the byte sequence does not match
the encoding expected by the server, which is controlled by
"client_encoding
CONTEXT: COPY logs, line 69238382
WARNING: errors ignored on restore: 1
Jesse Waters
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-09-05 19:30:37 | Re: SQL for Deleting all duplicate entries |
Previous Message | PSiegmann | 2007-09-05 19:13:26 | Is the ole db provider broken? |