| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Glyn Astill *EXTERN*" <glynastill(at)yahoo(dot)co(dot)uk>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: client_encoding error |
| Date: | 2007-11-28 10:39:29 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C2A0A90D@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Glyn Astill wrote:
> Whilst trying to migrate one of our tables to postgres we get the
> following error:
>
> invalid byte sequence for encoding "EUC_JP" : 0x9c32
> HINT: This error can also happen if the byte sequence does not match
> the enccding expected by the server, which is controlled by "client_encoding".
>
> Does anyone have any idea why this might be? The data cing into the
> table should be plain ASCII
It means that there is a string in your data which is incorrect
in your client encoding, which is EUC_JP.
You can only enter correctly encoded strings, everything else
will produce an error.
Your data is not plain ASCII, because the byte 0x9c is not
(0x9c > 0x7f).
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashish Karalkar | 2007-11-28 11:00:59 | Re: WAL Recovery |
| Previous Message | Sebastian - Anton PONOVESCU | 2007-11-28 10:26:53 | certificate based authorization |