pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Sam Barnett-Cormack <s.barnett-cormack@lancaster.ac.uk>
Cc: Rajesh Kumar Mallah <mallah@trade-india.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Tsearch1 problem
Date: Tue, 24 Feb 2004 10:39:36 -0500
Message-ID: <22428.1077637176@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.4.58.0402241717120.19870@ra.sai.msu.su>
References: <403B43A2.9040600@trade-india.com>
	<Pine.GSO.4.58.0402241640310.19870@ra.sai.msu.su>
	<Pine.LNX.4.50.0402241408430.438-100000@short.lancs.ac.uk>
	<Pine.GSO.4.58.0402241717120.19870@ra.sai.msu.su>

Oleg Bartunov <oleg@sai.msu.su> 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?

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



view thread (7+ messages)  latest in thread

Message-ID: <22428.1077637176@sss.pgh.pa.us>
Permalink:  ../22428.1077637176@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22428.1077637176@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, oleg@sai.msu.su, s.barnett-cormack@lancaster.ac.uk, mallah@trade-india.com
  Subject: Re: Tsearch1 problem
  In-Reply-To: <22428.1077637176@sss.pgh.pa.us>
  References: <403B43A2.9040600@trade-india.com> <Pine.GSO.4.58.0402241640310.19870@ra.sai.msu.su> <Pine.LNX.4.50.0402241408430.438-100000@short.lancs.ac.uk> <Pine.GSO.4.58.0402241717120.19870@ra.sai.msu.su> <22428.1077637176@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox