From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Peter Koczan" <pjkoczan(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Converting from SQL_ASCII to UTF8 |
Date: | 2007-11-29 22:14:18 |
Message-ID: | 19840.1196374458@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Peter Koczan" <pjkoczan(at)gmail(dot)com> writes:
> I have some UTF-8 data in my databases, and it's causing dump/restore
> to fail. Specifically, I'm seeing messages like:
> pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence
> for encoding "UTF8": 0xe14c65
This is, in fact, not UTF8, no matter how much you'd like to think so.
It might possibly be LATIN1 or some other single-byte encoding. What
you're going to need to do is figure out what you really have and
convert it all to a common encoding.
One of the disadvantages of SQL_ASCII mode is that it will let you wind
up with a mishmash of different encodings in your DB :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Campbell, Lance | 2007-11-30 19:46:53 | Enhancement request |
Previous Message | Milen A. Radev | 2007-11-29 21:52:27 | Re: clear statistics in pg_stat |