| Lists: | pgsql-hackers |
|---|
| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | confusing invalid UTF8 byte sequence error |
| Date: | 2011-08-28 12:04:43 |
| Message-ID: | 1314533083.4516.4.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
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.
| From: | Valentine Gogichashvili <valgog(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: confusing invalid UTF8 byte sequence error |
| Date: | 2011-08-29 15:03:29 |
| Message-ID: | CAP93muUiXM6M9Y20oBZD7F7GQ_m=Oh1gcKr3hNH3G8Ruv4Ng9w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
>
> 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...
-- Valentine Gogichashvili
| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Valentine Gogichashvili <valgog(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: confusing invalid UTF8 byte sequence error |
| Date: | 2011-08-29 15:30:07 |
| Message-ID: | CA+TgmoaSU9crBcCeax9SsWQR_K+urYLFnNFd7yx9cUL6b=9gvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On Mon, Aug 29, 2011 at 11:03 AM, Valentine Gogichashvili
<valgog(at)gmail(dot)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