pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Koczan <pjkoczan@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Converting from SQL_ASCII to UTF8
Date: Thu, 29 Nov 2007 17:14:18 -0500
Message-ID: <19840.1196374458@sss.pgh.pa.us> (raw)
In-Reply-To: <4544e0330711291337y4c875320r36414692972296a4@mail.gmail.com>
References: <4544e0330711291337y4c875320r36414692972296a4@mail.gmail.com>

"Peter Koczan" <pjkoczan@gmail.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



view thread (2+ messages)

Message-ID: <19840.1196374458@sss.pgh.pa.us>
Permalink:  ../19840.1196374458@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19840.1196374458@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pjkoczan@gmail.com
  Subject: Re: Converting from SQL_ASCII to UTF8
  In-Reply-To: <19840.1196374458@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox