Re: confusing invalid UTF8 byte sequence error - Mailing list pgsql-hackers

From Robert Haas
Subject Re: confusing invalid UTF8 byte sequence error
Date
Msg-id CA+TgmoaSU9crBcCeax9SsWQR_K+urYLFnNFd7yx9cUL6b=9gvA@mail.gmail.com
Whole thread Raw
In response to Re: confusing invalid UTF8 byte sequence error  (Valentine Gogichashvili <valgog@gmail.com>)
List pgsql-hackers
On Mon, Aug 29, 2011 at 11:03 AM, Valentine Gogichashvili
<valgog@gmail.com> wrote:
>> Has anyone else ever found this error message confusing:
>> ERROR:  22021: invalid byte sequence for encoding "UTF8": 0xdb24
>> I think what is really meant is better expressed like this:
>> ERROR:  22021: invalid byte sequence for encoding "UTF8": 0xdb 0x24
>> Otherwise it looks like a codepoint or a 16-bit word (endianness?) or
>> who knows what.
>
> Talking about this error, I find the lack of context in this error message
> more confusing... relative position or surrounding charachters would be
> really helpful, when searching for a problem with encoding...

+1.  Twiddling with the exact wording of the error message doesn't
seem likely to make a huge difference in terms of usability, but
providing some more context would be *really* helpful.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: spinlocks on HP-UX
Next
From: Tom Lane
Date:
Subject: Re: spinlocks on HP-UX