Paul, To fix your dump so it will import, run:
iconv -c -f UTF8 -t UTF8 -o fixed.sql dump.sql Kind Regards, John Hansen > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Paul Lindner > Sent: Sunday, October 23, 2005 1:34 AM > To: pgsql-bugs@postgresql.org > Subject: [BUGS] BUG #1987: UTF8 encoding differences hamper upgrades > > > The following bug has been logged online: > > Bug reference: 1987 > Logged by: Paul Lindner > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1beta3 > Operating system: Fedora Core 4 x86_64 > Description: UTF8 encoding differences hamper upgrades > Details: > > I've been doing some test imports of UNICODE databases into > Postgres > > > > 8.1beta3. The only problem I've seen is that some data from > 8.0 > > > > databases will not import. > > > > > > > > > > I've generated dumps using pg_dump from 8.0 and 8.1. > Attempting to > > > > restore these results in > > > > > > > > > > Invalid UNICODE byte sequence detected near byte ... > > > > > > > > > > Question: > > > > > > > > > > Does the 8.1 Unicode sanity code accept the full set of > characters > > > > accepted by the 8.0 Unicode sanity code? > > > > > > > > > > If not we'll see a lot of problems like the one above. > > > > > > > > > > > > > > > I believe this patch is the one causing the problem I see: > > > > > > > > > > > http://www.mail-archive.com/pgsql-patches@postgresql.org/msg08 198/unicode.di > ff > > > > > > > > > > > > > Is there any solution other than scrubbing the entire dataset > to > > > > conform to the new (8.1) encoding rules? > > ---------------------------(end of > broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > > ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
