From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
---|---|
To: | Benjamin Krajmalnik <kraj(at)illumen(dot)com> |
Cc: | "pgsql admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Strange UTF8 issue with pg_dump/pg_restore |
Date: | 2006-08-08 16:48:37 |
Message-ID: | 773783AD-1DEC-411E-9BF1-16293664A090@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Aug 7, 2006, at 9:08 PM, Benjamin Krajmalnik wrote:
> I have a database whose records are inserted via ODBC.
> I turned on logging, and the client is explicitly setting the
> client encoding to UTF.
>
> Rows are inserted into the tables. When I do a pg_dump, I do not
> get any errors. When I try tor restore, I am getting an error
> regarding an invalid UTF-8 character sequence.
> Of course, this renders compressed backups useless, since I have no
> way of manually fixing the file. The process of fixing the file
> is, of course, painful.
>
> Is this a known issue? I am running PG 8.1.4. The problem
> happened on PG Windows.
> Tomorrow I will try to see if the problem exists in the FreeBSD
> compile. If I get it to reproduce, I will be able to send some
> data dumps, but will need to know who to send it to.
Are the dumps from an older version? There's a known issue that older
versions weren't doing proper checking, in which case you can have
invalid UTF8 characters. The fix is to run the dump through iconv.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-08-08 16:48:56 | Re: File system backup question |
Previous Message | Jim Nasby | 2006-08-08 16:48:13 | Re: Getting rid of postgres output |