| From: | Marcin Stępnicki <mstepnicki(at)gmail(dot)com> |
|---|---|
| To: | "Hari, Balaji" <Balaji_Hari(at)bmc(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: LIKE Query performance |
| Date: | 2009-01-28 09:27:18 |
| Message-ID: | 179149fe0901280127l1d1ec452x3ac1a8947ee66b64@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Jan 28, 2009 at 12:41 AM, Hari, Balaji <Balaji_Hari(at)bmc(dot)com> wrote:
> EXPLAIN ANALYZE SELECT event_id, category, current_session_number,
> description, event_type_id, realm_name, root_session_number, severity,
> source_name, target_key, target_name, timestamp, jdo_version FROM event
> WHERE description like '%mismatch%' ORDER BY timestamp desc;
(...)
> Is there any tweaks to force pgsql to use index on description?
How long is usually the description? For me it sounds like the job for
tsearch2 module, which should be in "contrib" section in 8.1.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A. Kretschmer | 2009-01-28 09:43:19 | Re: LIKE Query performance |
| Previous Message | Rohan Pethkar | 2009-01-28 09:14:55 | Need help in setting up DBT2 for PostgreSQL |