| From: | Andreas Kostyrka <andreas(at)mtg(dot)co(dot)at> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Index not used, performance problem |
| Date: | 2003-03-29 16:57:58 |
| Message-ID: | 1048957078.7539.17.camel@andi-lap |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sat, 2003-03-29 at 14:47, Christopher Kings-Lynne wrote:
> As for the LIKE searches, the only ones that PostgreSQL can index are of
> the form 'FOO%', which is what you are doing. However, I believe that
> PostgreSQL cannot do this if your database encoding is anything other than
> 'C'. So, if you are using an Austrian encoding, it might not be able to
> use the index.
Well, I use LATIN1. How do I store 8-bit chars else? And if so,
PostgreSQL seems quite strongly broken, because a relational database
relies by design heavily on indexes.
> Also, what is the point of searching for LIKE '%'? Why not just leave that
> out?
Well, it's about generating the SQL query.
Actually it's just a border case for searching for a given prefix.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kostyrka | 2003-03-29 16:59:11 | Re: Index not used, performance problem |
| Previous Message | John K. Herreshoff | 2003-03-29 16:49:00 | Re: Index not used, performance problem |