Re: invalid byte sequence for encoding "UTF8": 0xff - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: invalid byte sequence for encoding "UTF8": 0xff
Date
Msg-id 20070903081556.GA20844@svana.org
Whole thread Raw
In response to invalid byte sequence for encoding "UTF8": 0xff  ("Ashish Karalkar" <ashish.karalkar@info-spectrum.com>)
List pgsql-general
On Mon, Sep 03, 2007 at 01:36:58PM +0530, Ashish Karalkar wrote:
> Hello All,
>
> I have a data script which runs fine from PgAdmin SQL Editor,but when I  run this  from command prompt I get
followingerror: 
> test=# \i /usr/local/pgsql/qsweb1/QSWEB_100_4_Default_Data.sql
>
> psql:/usr/local/pgsql/qsweb1/QSWEB_100_4_Default_Data.sql:1: ERROR:  invalid byt
> e sequence for encoding "UTF8": 0xff
> HINT:  This error can also happen if the byte sequence does not match the encodi
> ng expected by the server, which is controlled by "client_encoding".

Well, the error is correct, that's not a valid UTF-8 character. I seem
to remember someone saying that ooasionally windows puts BOMs in UTF-8
files (which is completely bogus). Check the file using a simple text
editor a check if there are some odd characters at the beginning of the
file.

Have a ncie day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: "Ashish Karalkar"
Date:
Subject: invalid byte sequence for encoding "UTF8": 0xff
Next
From: Ow Mun Heng
Date:
Subject: Instances where enable_seqscan = false is good