On Mon, Aug 29, 2011 at 11:03 AM, Valentine Gogichashvili
>> 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.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2011-08-29 15:42:28|
|Subject: Re: spinlocks on HP-UX |
|Previous:||From: Robert Haas||Date: 2011-08-29 15:29:16|
|Subject: Re: spinlocks on HP-UX|