From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Geoffrey Myers <lists(at)serioustechnology(dot)com> |
Subject: | Re: error while trying to change the database encoding on a database |
Date: | 2011-01-24 15:55:32 |
Message-ID: | 201101240755.33062.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday 24 January 2011 6:38:55 am Geoffrey Myers wrote:
> We need to change the database encoding on our databases as they were
> created with the wrong encoding. They were created as SQL_ASCII and we
> are changing them to UTF8.
>
> When testing this Friday, I received the following error:
>
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 5225; 0 16990 TABLE
> DATA cust postgres
> pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence
> for encoding "UTF8": 0xb0
> HINT: This error can also happen if the byte sequence does not match
> the encoding expected by the server, which is controlled by
> "client_encoding".
> CONTEXT: COPY cust, line 778
^^^^^^^ In the COPY command for that table.
>
> Is there any easy way to figure out which record caused this error?
>
> Thanks.
>
> --
> Until later, Geoffrey
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-01-24 15:56:35 | Re: (Hopefully stupid) select question. |
Previous Message | Fredric Fredricson | 2011-01-24 15:50:33 | (Hopefully stupid) select question. |