X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 846D6D1E125 for ; Tue, 24 Feb 2004 15:39:39 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 82008-04 for ; Tue, 24 Feb 2004 11:39:36 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id EEB3ED1E0DD for ; Tue, 24 Feb 2004 11:39:31 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1OFdaCr022429; Tue, 24 Feb 2004 10:39:36 -0500 (EST) To: Oleg Bartunov Cc: Sam Barnett-Cormack , Rajesh Kumar Mallah , pgsql-admin@postgresql.org Subject: Re: Tsearch1 problem In-reply-to: References: <403B43A2.9040600@trade-india.com> Comments: In-reply-to Oleg Bartunov message dated "Tue, 24 Feb 2004 17:25:34 +0300" Date: Tue, 24 Feb 2004 10:39:36 -0500 Message-ID: <22428.1077637176@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/343 X-Sequence-Number: 12517 Oleg Bartunov 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