Re: Tsearch + polish ispell + polish locale - Mailing list pgsql-hackers

From
Subject Re: Tsearch + polish ispell + polish locale
Date
Msg-id EA6A3F5C1E4BC14D91D93A344436440C010D32C2@MXMBON01.grupa.onet
Whole thread Raw
In response to Re: Tsearch + polish ispell + polish locale  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Tsearch + polish ispell + polish locale
List pgsql-hackers
Hi Teodor,

Unfortunately I can't create test suite ...
I tried to create it as simple as possibile, but on simple (small) database everything works fine.
I also cannot provide you mirror of my database since it contains proprietary data ...

I solved my problem by creating my own tolower() function and replace it over the tsearch2 code.
On database with locale set to 'C' it works fine.

As far As I debugged the problem I could observe that with locale = 'C' RS_compile() is fed only with strings that does
notcontain polish letters. 
With locale set to 'pl_PL.iso88592' strings passed to PS_compile contain polish letters.
I do not know how, but in some strange, random cases function isalpha() stops return true value for polish letters, and
thatis when RS_compile() returns error. 

I will try to compile and run my database on the CVS version of postgres, and let you know the results.

Is it safe to use 8.2 version over 8.1.5 database files ?

BTW. When the official 8.2 release is expected ?

Thanks for your time and engagement,Arek.

PS. BTW I have found minor inconsistency in the regis.c code (CVS version)   Return value type is not as it should ..
seesnippet below... 

170 bool
171 RS_execute(Regis * r, char *str)
[...]
183 >>>>>>>>if (len < r->nchar)
184 >>>>>>>>>>>>>>>>return 0;




pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: quick review
Next
From: "Simon Riggs"
Date:
Subject: Re: [GENERAL] statement_timeout