X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 99A49D1BC59 for ; Mon, 22 Sep 2003 16:55:42 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 64407-02 for ; Mon, 22 Sep 2003 13:55:12 -0300 (ADT) Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by svr1.postgresql.org (Postfix) with ESMTP id AA7D4D1BBA4 for ; Mon, 22 Sep 2003 13:55:11 -0300 (ADT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-34.mail.demon.net with esmtp (Exim 3.35 #1) id 1A1Txv-000NUl-0Y; Mon, 22 Sep 2003 17:55:11 +0100 Received: from localhost (localhost.localdomain [127.0.0.1]) by mainbox.archonet.com (Postfix) with ESMTP id BC4D116AFA; Mon, 22 Sep 2003 17:55:10 +0100 (BST) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id EDFF41677A; Mon, 22 Sep 2003 17:55:09 +0100 (BST) From: Richard Huxton To: Wei Weng Subject: Re: GiST and full text search Date: Mon, 22 Sep 2003 17:55:09 +0100 User-Agent: KMail/1.5 Cc: pgsql-sql@postgresql.org References: <200309221624.01700.dev@archonet.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309221755.09838.dev@archonet.com> X-Virus-Scanned: by AMaViS snapshot-20020531 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/259 X-Sequence-Number: 15237 On Monday 22 September 2003 16:41, Wei Weng wrote: > The production server uses PostgreSQL 7.3.1 right now, so I am only > looking at contrib/tsearch. > > I read through the README file. It only seems to offer a way to FTS > through one 'text' column in the table. How do I create a 'txtidx' column > that combines two or even more 'text' columns in the table? According to README.tsearch from 7.4beta (not tsearch2 which is the new one) Current syntax allows creating trigger for several columns you want to be searchable: create trigger txtidxupdate before update or insert on titles for each row execute procedure tsearch(titleidx, title1, title2,... ); Perhaps see what 7.3.4's tsearch says - that should be compatible with 7.3.1 -- Richard Huxton Archonet Ltd