X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6A8009DCAF0 for ; Wed, 7 Dec 2005 04:28:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 18849-07 for ; Wed, 7 Dec 2005 04:28:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id C5E589DCAE1 for ; Wed, 7 Dec 2005 04:28:50 -0400 (AST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id BFC303093C; Wed, 7 Dec 2005 09:28:51 +0100 (MET) From: Michael Riess X-Newsgroups: pgsql.performance Subject: Re: TSearch2 vs. Apache Lucene Date: Wed, 07 Dec 2005 09:28:52 +0100 Organization: Hub.Org Networking Services Lines: 27 Message-ID: References: <43963D9B.4020605@familyhealth.com.au> <43969B31.5070904@familyhealth.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.5 (Windows/20051025) In-Reply-To: <43969B31.5070904@familyhealth.com.au> To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/225 X-Sequence-Number: 16046 Christopher Kings-Lynne schrieb: >> No, my problem is that using TSearch2 interferes with other core >> components of postgres like (auto)vacuum or dump/restore. > > That's nonsense...seriously. > > The only trick with dump/restore is that you have to install the > tsearch2 shared library before restoring. That's the same as all > contribs though. Well, then it changed since I last read the documentation. That was about a year ago, and since then we are using Lucene ... and as it works quite nicely, I see no reason to switch to TSearch2. Including it with the pgsql core would make it much more attractive to me, as it seems to me that once included into the core, features seem to be more stable. Call me paranoid, if you must ... ;-) > > Chris > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >