Re: error while trying to change the database encoding on a database

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: error while trying to change the database encoding on a database
Date: 2011-01-28 21:00:21
Message-ID: ihvap5$7t3$3@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2011-01-24, Geoffrey Myers <lists(at)serioustechnology(dot)com> wrote:
> Adrian Klaver wrote:

> Thanks for the suggestion. As it stands, we are getting different
> errors for different hex characters, thus the solution we need is the
> ability to identify the characters that won't convert from SQL_ASCII to
> UTF8. Is there a resource that would identify these characters?

use "iconv" to strip out the invalid chacaters from the SQL and then
compare before and after.

I think the iconv command is

iconv -f UTF8 -t UTF8 -c

--
⚂⚃ 100% natural

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2011-01-28 21:12:28 Re: Full Text Index Scanning
Previous Message Jasen Betts 2011-01-28 20:51:38 Re: Dumpall without OID