Re: integrated tsearch has different results than tsearch2

2007/9/3, Teodor Sigaev <teodor@sigaev.ru>:
> > 1. I am not able use fulltext with latin2 encoding :( I missing note
> > about only utf8 dictionaries in doc).
> You can use any server encoding, but dictionary's files should be in utf8 -
> dictionary will convert utf8 files into server encoding.
>
> >
> >
> > 2. with hspell dictionaries (fresh copy from open office) I got
> > different and wrong results.
> > postgres=# select to_tsvector('cs','Příliš žlutý kůň se napil žluté
> > vody') @@ to_tsquery('cs','napít');
> >  ?column?
> > ----------
> >  f
> > (1 row)
>
> Pls, output of:
> select ts_lexize('cspell','napil');
> select to_tsvector('cs','Příliš žlutý kůň se napil žluté
> vody');
>
>
postgres=# select ts_lexize('cspell','napil');ts_lexize
-----------

(1 row)
postgres=# select to_tsvector('cs','Příliš žlutý kůň se napil žluté vody');                       to_tsvector
-----------------------------------------------------------'vody':7 'kůň':3 'napil':5 'žluté':6 'žlutý':2 'příliš':1
(1 row)

There is difference
8.2.x
postgres=# select lexize('cz_ispell','jablka'); lexize
----------{jablko}
(1 row)
8.3
postgres=# select ts_lexize('cspell','jablka');ts_lexize
-----------

(1 row)
postgres=# select ts_lexize('cspell','jablko');ts_lexize
-----------{jablko}
(1 row)

Pavel Stehule