Received: from dfw-ix14.ix.netcom.com (dfw-ix14.ix.netcom.com [206.214.98.14]) by hub.org (8.9.3/8.9.3) with ESMTP id TAA89683 for ; Wed, 11 Aug 1999 19:34:20 -0400 (EDT) (envelope-from drfrog@smartt.com) Received: (from smap@localhost) by dfw-ix14.ix.netcom.com (8.8.4/8.8.4) id SAA29134; Wed, 11 Aug 1999 18:30:29 -0500 (CDT) Received: from 00-10-4b-66-ed-f1.bconnected.net(209.53.23.202) by dfw-ix14.ix.netcom.com via smap (V1.3) id rma029112; Wed Aug 11 18:30:07 1999 Sender: DrFrog@ix.netcom.com Message-ID: <37B20977.B560E075@smartt.com> Date: Wed, 11 Aug 1999 23:38:31 +0000 From: Clayton Cottingham X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.3.2 i586) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: pgsql-sql@postgreSQL.org Subject: Re: [SQL] quest:optimization with indexes References: <9515.934410946@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Tom Lane wrote: > Clayton Cottingham writes: > > thanks for all those 'like' tips i was wonderinng, would using regex be the > > same as far as the indexing rules go? > > It's equivalent --- an index can help if the pattern is anchored to the > start of the string. Of course the pattern notation is different... > > regards, tom lane what about helper software like glimpse, as per my other thread? i was told to use glimpse, because full text index {fti} isnt robust enough to handle large db's what do you think the most optimized way of handling this sort of thing would be?