Re: invalid byte sequence for encoding "UTF8"

From: Alan Hodgson <ahodgson(at)simkin(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: invalid byte sequence for encoding "UTF8"
Date: 2007-03-21 16:54:41
Message-ID: 200703210954.41919@hal.medialogik.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday 21 March 2007 04:17, "Fuzzygoth" <dav(dot)phillips(at)ntlworld(dot)com>
wrote:
> I've searched the forums and found people with similar problems but
> not much
> on a way to remedy it. I did try using iconv which was suggested in a
> thread
> but it returned an error saying even the 22GB file was too large to
> work on.

iconv needs to read the whole file into RAM. What you can do is use the
UNIX split utility to split the dump file into smaller segments, use iconv
on each segment, and then cat all the converted segments back together into
a new dump file. iconv is I think your best option for converting the dump
to a valid encoding.

--
"None are more hopelessly enslaved than those who falsely believe they are
free." -- Johann W. Von Goethe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Browne 2007-03-21 17:01:03 Re: SoC Ideas for people looking for projects
Previous Message Ron Johnson 2007-03-21 16:50:15 Re: Anyone still using the sql_inheritance parameter?