Re: BUG #15476: Problem on show_trgm with 4 byte UTF-8 characters
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #15476: Problem on show_trgm with 4 byte UTF-8 characters |
| Дата | |
| Msg-id | 2101.1541220270@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | BUG #15476: Problem on show_trgm with 4 byte UTF-8 characters (PG Bug reporting form <noreply@postgresql.org>) |
| Список | pgsql-bugs |
=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> On Encoding=UTF-8 database, try:
> SELECT show_trgm('123');
> → OK
> SELECT show_trgm('日本語');
> → probably OK.
> SELECT show_trgm('🔍');
> ERROR: invalid multibyte character for locale
> HINT: The server's LC_CTYPE locale is probably incompatible with the
> database encoding.
> SQL state: 22021
I failed to reproduce this on a Linux machine. It looks to me like the
problem is that Windows' MultiByteToWideChar doesn't think that UTF8
character is valid.
> Please check: t_isdigit, t_isspace, t_isalpha, and t_isprint.
>
https://github.com/postgres/postgres/blob/322548a8abe225f2cfd6a48e07b99e2711d28ef7/src/backend/tsearch/ts_locale.c#L35
> char2wchar 4th parameter should take number of input bytes. However they
> pass character count.
> int clen = pg_mblen(ptr);
> ...
> char2wchar(character, 2, ptr, clen, mylocale);
Huh? pg_mblen returns the number of bytes in a multibyte character,
so this looks fine to me.
regards, tom lane
В списке pgsql-bugs по дате отправления: