integrated tsearch doesn't work with non utf8 database
От | Pavel Stehule |
---|---|
Тема | integrated tsearch doesn't work with non utf8 database |
Дата | |
Msg-id | 162867790709071213o898ce7av333a570bd9004f27@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: integrated tsearch doesn't work with non utf8 database
|
Список | pgsql-hackers |
Hello last time I checked utf8 database. Now I checked latin2 encoding database. I used dictionaries from last test. client_encoding | utf8 lc_collate | cs_CZ.iso-8859-2 lc_ctype | cs_CZ.iso-8859-2 lc_messages | cs_CZ.iso-8859-2 lc_monetary | cs_CZ.iso-8859-2 lc_numeric | cs_CZ.iso-8859-2 lc_time | cs_CZ.iso-8859-2 postgres=# create Text search dictionary cspell2(template=ispell, afffile=czech, dictfile=czech); CREATE TEXT SEARCH DICTIONARY postgres=# alter text search configuration cs alter mapping for word, lword with cspell2, simple; ALTER TEXT SEARCH CONFIGURATION postgres=# select ts_debug('cs','Příliš žluťoučký kůň se napil žluté vody'); ERROR: character 0xc3a5 of encoding "UTF8" has no equivalent in "LATIN2" CONTEXT: SQL function "ts_debug" statement 1 postgres=# database was initialised /usr/local/pgsql/bin/initdb --encoding=latin2 --locale=cs_CZ.iso-8859-2 -D /usr/local/pgsql/data/ locales is correct postgres=# set client_encoding to utf8; SET postgres=# select upper('Příliš žluťoučký kůň se napil žluté vody'); upper ------------------------------------------PŘÍLIŠ ŽLUŤOUČKÝ KŮŇ SE NAPIL ŽLUTÉ VODY (1 row) Regards Pavel Stehule
В списке pgsql-hackers по дате отправления: