Re: Upcoming PG re-releases - Mailing list pgsql-hackers

From Paul Lindner
Subject Re: Upcoming PG re-releases
Date
Msg-id 20051204164054.GE10317@inuus.com
Whole thread Raw
In response to Re: Upcoming PG re-releases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Upcoming PG re-releases
List pgsql-hackers
On Sun, Dec 04, 2005 at 11:34:16AM -0500, Tom Lane wrote:
> Paul Lindner <lindner@inuus.com> writes:
> > To convert your pre-8.1 database to 8.1 you may have to remove and/or
> > fix the offending characters.  One simple way to fix the problem is to
> > run your pg_dump output through the iconv command like this:
>
> >   iconv -c -f UTF8 -t UTF8 -o fixed.sql dump.sql
>
> Is that really a one-size-fits-all solution?  Especially with -c?
>

I'd say yes, and the -c flag is needed so iconv strips out the
invalid characters.

This technique worked for some smaller databases I converted and
croaked with out-of-memory on the larger ones.

It certainly doesn't make the problem worse.

If one wanted to fix this in the general case one could duplicate the
iconv behavior in the Postgres code via some kind of special
flag/setting that is only used for imports..
 set strip_bad_utf8 = on


--
Paul Lindner        ||||| | | | |  |  |  |   |   |
lindner@inuus.com

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Upcoming PG re-releases
Next
From: Tom Lane
Date:
Subject: Re: Upcoming PG re-releases