X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EE9C5D1B49C for ; Thu, 27 Nov 2003 01:04:31 +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 03659-02 for ; Wed, 26 Nov 2003 21:04:09 -0400 (AST) Received: from rlx13.zapatec.com (66-117-144-213.zapatec.lmi.net [66.117.144.213]) by svr1.postgresql.org (Postfix) with ESMTP id E663BD1B448 for ; Wed, 26 Nov 2003 21:03:59 -0400 (AST) Received: from rlx11.zapatec.com (rlx11.pr.zapatec.com [192.168.1.132]) by rlx13.zapatec.com (Postfix) with ESMTP id 8A4F6A941 for ; Wed, 26 Nov 2003 17:03:53 -0800 (PST) Received: (from dror@localhost) by rlx11.zapatec.com (8.12.3/8.12.3/Submit) id hAR13qsa044103 for pgsql-performance@postgresql.org; Wed, 26 Nov 2003 17:03:52 -0800 (PST) (envelope-from dror) Date: Wed, 26 Nov 2003 17:03:52 -0800 From: Dror Matalon To: pgsql-performance@postgresql.org Subject: Re: For full text indexing, which is better, tsearch2 or Message-ID: <20031127010352.GT30893@rlx11.zapatec.com> References: <4c0ccf4c27ff.4c27ff4c0ccf@jhmimail.jhmi.edu> <3FC54A82.2040605@familyhealth.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FC54A82.2040605@familyhealth.com.au> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/286 X-Sequence-Number: 4846 On Thu, Nov 27, 2003 at 08:51:14AM +0800, Christopher Kings-Lynne wrote: > >Which one is better (performance/easier to use), > >tsearch2 or fulltextindex? > >there is an example how to use fulltextindex in the > >techdocs, but I checked the contrib/fulltextindex > >package, there is a WARNING that fulltextindex is > >much slower than tsearch2. but tsearch2 seems > >complex to use, and I can not find a good example. > >Which one I should use? Any suggestions? > > I believe I wrote that warning :) > > Tsearch2 is what you should use. Yes, it's more complicated but it's > HEAPS faster and seriously powerful. > Can you provide some numbers please, both for creating full text indexes as well as for searching them? I tried to use tsearch and it seemed like just creating a full text index on million+ records took forever. > Just read the README file. > > You could also try out the original tsearch (V1), but that will probably > be superceded soon, now that tsearch2 is around. > > Chris > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html -- Dror Matalon Zapatec Inc 1700 MLK Way Berkeley, CA 94709 http://www.fastbuzz.com http://www.zapatec.com