On Tue, 24 Feb 2004, Tom Lane wrote:
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
> > Also, I run test on 7.3.3
> > Everything is ok.
> > I see your version of postgresql is outdated (you may upgrade at least
> > to 7.3.5 !) and most suspicious is the version of your compiler 2.96 !
>
> There was at least one post-7.3 bug fix in tsearch, according to the CVS
> logs. Could this be it?
Most probable !
>
> 2002-12-06 00:15 momjian
>
> * contrib/tsearch/morph.c (REL7_3_STABLE): Thank you very much, you
> catch it :). This bug had a long life, because it exists if and
> only if locale of postmaster was a different from C (or
> ru_RU.KOI8-R).
>
> Please, apply patch for current CVS & 7.3.1
>
> Magnus Naeslund(f) wrote:
> > Ok, I nailed the bug, but i'm not sure what the correct fix is.
> > Attached tsearch_morph.diff that remedies this problem by
> avoiding it.
> > Also there's a debug aid patch if someone would like to know how
> i
> > finally found it out :)
> >
> > There problem in the lemmatize() function is that GETDICT(...)
> returned
> > a value not handled (BYLOCALE).
> > The value (-1) and later used as an index into the dicts[] array.
> > After that everything went berserk stack went crazy somehow so
> trapping
> > the fault sent me to the wrong place, and every time i read the
> value it
> > was positive ;)
> >
> > So now i just return the initial word passed to the lemmatize
> function,
> > because i don't know what to do with it.
>
> Magnus Naeslund
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
