Skip site navigation (1) Skip section navigation (2)

Re: confusing invalid UTF8 byte sequence error

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 (view raw or flat)
Thread:
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

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-08-29 15:42:28
Subject: Re: spinlocks on HP-UX
Previous:From: Robert HaasDate: 2011-08-29 15:29:16
Subject: Re: spinlocks on HP-UX

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group