Re: Performance for seq. scans

At 12:28 26/07/00 +0100, Jules Bean wrote:
>> We were in a similar position and went for the 'Full Text Indexing" extra.
>> You'll find it in contrib/fulltextindex.
>> It creates a function which you call on a trigger to produce an index of
>> words for specified fields. These indexes do get _very_ large (one of ours
>> is ~800 MB), but it does work very well and speeds searches up enormously.
>
>If I understand you correctly, that's word-based? It's just splitting
>on whitespace and punctuation? Unfortunately, that's not quite what
>we need --- our wildcard searches needn't have their '%' on word
>boundaries.
>

There is a function in the source called breakup(). This can be customised
to create the index entries on sub-word strings.

Steve

--
thorNET - Internet Consultancy, Services & Training
Phone: 01454 854413
Fax: 01454 854412
http://www.thornet.co.uk