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 6F2B8D1B44F for ; Tue, 25 Nov 2003 21:29:37 +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 37579-09 for ; Tue, 25 Nov 2003 17:29:06 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 671F0D1B474 for ; Tue, 25 Nov 2003 17:29:05 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hAPLT419008755; Tue, 25 Nov 2003 16:29:04 -0500 (EST) To: josh@agliodbs.com Cc: LIANHE SHAO , pgsql-performance@postgresql.org Subject: Re: why index scan not working when using 'like'? In-reply-to: <200311251151.40781.josh@agliodbs.com> References: <3d83693d9fe0.3d9fe03d8369@jhmimail.jhmi.edu> <200311251151.40781.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Tue, 25 Nov 2003 11:51:40 -0800" Date: Tue, 25 Nov 2003 16:29:04 -0500 Message-ID: <8754.1069795744@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/253 X-Sequence-Number: 4813 Josh Berkus writes: > In regular text fields containing words, your problem is solvable with full > text indexing (FTI). Unfortunately, FTI is not designed for arbitrary > non-language strings. It could be adapted, but would require a lot of > hacking. I'm not sure why you say that FTI isn't a usable solution. As long as the gene symbols are separated by whitespace or some other non-letters (eg, "foo mif bar" not "foomifbar"), I'd think FTI would work. regards, tom lane