From: | Steve Heaven <steve(at)thornet(dot)co(dot)uk> |
---|---|
To: | Jules Bean <jules(at)jellybean(dot)co(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Performance for seq. scans |
Date: | 2000-07-26 11:14:13 |
Message-ID: | 3.0.1.32.20000726121413.0071dbc0@mail.thornet.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 11:51 26/07/00 +0100, you wrote:
>Hi all,
>
>I've had a look over the docs and the FAQ and I can't see anything
>answering this, so here goes:
>
>I'm in the (slightly unusual, in a relational world) situation that
>the dominant query on my database is a wildcard search, so that no
>indexes can be used. (E.g. select * from table_a where foo like
>'%bar%').
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.
Steve
--
thorNET - Internet Consultancy, Services & Training
Phone: 01454 854413
Fax: 01454 854412
http://www.thornet.co.uk
From | Date | Subject | |
---|---|---|---|
Next Message | Jules Bean | 2000-07-26 11:28:18 | Re: Performance for seq. scans |
Previous Message | Andrea Aime | 2000-07-26 11:06:21 | Re: Connecting to PostgreSQL databases |