X-Original-To: pgsql-sql-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 591889FA13E for ; Tue, 13 Jun 2006 17:51:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 25439-06 for ; Tue, 13 Jun 2006 17:51:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from peufeu.com (boutiquenumerique.com [82.67.9.10]) by postgresql.org (Postfix) with ESMTP id 6C7639F9316 for ; Tue, 13 Jun 2006 17:51:37 -0300 (ADT) Received: (qmail 15173 invoked from network); 13 Jun 2006 22:52:40 +0200 Received: from boutiquenumerique.com (HELO apollo13) (82.67.9.10) by boutiquenumerique.com with SMTP; 13 Jun 2006 22:52:40 +0200 To: "Aaron Bono" , PostgreSQL Subject: Re: Efficient Searching of Large Text Fields References: Message-ID: Date: Tue, 13 Jun 2006 22:52:39 +0200 From: PFC Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Opera M2/8.54 (Linux, build 1745) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/138 X-Sequence-Number: 25374 > 2. What functions or libraries are available to make such searching > easy to implement well? the tsearch2 module does that, and has a substantial advantage over a solution you might reimplement : it's already done (and it works). Try it...