Re: [GENERAL] GiST index slower than seqscan

2006-04-21 Thread Teodor Sigaev
When I said full text, I meant substring. Please correct me if I am wrong, but tsearch would be useful for finding words in a paragraph, not characters in a word (or small group of words) ... If I had fields 'Hello World!', 'Low Tide', and 'Following Day' they would all be hits for a search on

Re: [GENERAL] GiST index slower than seqscan

2006-04-21 Thread CG
--- Teodor Sigaev <[EMAIL PROTECTED]> wrote: > > In case you're unfamiliar with this particular horse, I'm using ltree to > create > > a full text index on some <= 50 char long fields for a lookup table. The > idea > > was to be able to tear through tons of data quickly finding case > insensitiv

Re: [GENERAL] GiST index slower than seqscan

2006-04-20 Thread Teodor Sigaev
In case you're unfamiliar with this particular horse, I'm using ltree to create a full text index on some <= 50 char long fields for a lookup table. The idea was to be able to tear through tons of data quickly finding case insensitive substring matches. Why it is a ltree, not a tsearch?