Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 868EC9FB82E for ; Tue, 27 Feb 2007 19:36:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 53657-10 for ; Tue, 27 Feb 2007 19:36:23 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from xena.bway.net (xena.bway.net [216.220.96.26]) by postgresql.org (Postfix) with ESMTP id E30CC9FB7F3 for ; Tue, 27 Feb 2007 19:36:22 -0400 (AST) Received: (qmail 58284 invoked by uid 0); 27 Feb 2007 23:36:21 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (216.220.116.154) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Feb 2007 23:36:21 -0000 Date: Tue, 27 Feb 2007 18:36:11 -0500 (EST) From: Charles Sprickman X-X-Sender: spork@white.nat.fasttrackmonkey.com To: Dave Page cc: Magnus Hagander , Madison Kelly , pgsql-performance@postgresql.org Subject: Re: Writting a "search engine" for a pgsql DB In-Reply-To: <45E4333B.9020008@postgresql.org> Message-ID: References: <45E30ADA.2050700@alteeve.com> <20070227131558.GP12721@svr2.hagander.net> <45E4333B.9020008@postgresql.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.186 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200702/335 X-Sequence-Number: 23389 On Tue, 27 Feb 2007, Dave Page wrote: > Magnus Hagander wrote: >> >> Just as a datapoint, we did try to use mnogosearch for the >> postgresql.org website+archives search, and it fell over completely. >> Indexing took way too long, and we had search times several thousand >> times longer than with tsearch2. >> >> That said, I'm sure there are cases when it works fine :-) > > There are - in fact before your time the site did use Mnogosearch. We > moved to our own port of ASPSeek when we outgrew Mnogo's capabilities, > and then to your TSearch code when we outgrew ASPSeek. At risk of pulling this way too far off topic, may I ask how many documents (mail messages) you were dealing with when things started to fall apart with mnogo? We're looking at it for a new project that will hopefully get bigger and bigger. We will be throwing groups of mailing lists into their own mnogo config/tables... If we should save ourselves the pain and look at something more homebrew, then we'll start investigating "Tsearch". Thanks, Charles > When we outgrow PostgreSQL & Tsearch2, then, well, we'll need to stop > pretending to be Google... > > /D > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend >