From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: like/ilike improvements |
Date: | 2007-09-22 11:20:24 |
Message-ID: | 1d4e0c10709220420y4edb7bfeufa859a37f47224aa@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On 9/22/07, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> wrote:
> Anyway, I'm starting with a clean tree containing your fix and what
> Tom commited but I have to import the data again due to the catalog
> version bump :).
I have some good news. After Andrew's and Greg's patches, CVS HEAD is
as fast as 8.2 with latin1 encoding:
cityvox_latin1=# SELECT e.numeve FROM evenement e WHERE e.libgeseve
LIKE '%hocus pocus%';
numeve
--------
(0 rows)
Time: 102.731 ms
cityvox_latin1=# SELECT e.numeve FROM evenement e WHERE e.libgeseve
ILIKE '%hocus pocus%';
numeve
-----------
900024298
87578
(2 rows)
Time: 120.399 ms
So the only regression left is that from 8.2, ILIKE with UTF-8
encoding is really slower than before but it doesn't seem easy to
solve (if possible).
Regards,
--
Guillaume
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-22 15:38:52 | Re: First steps with 8.3 and autovacuum launcher |
Previous Message | Guillaume Smet | 2007-09-22 10:06:57 | Re: First steps with 8.3 and autovacuum launcher |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-09-22 14:41:54 | ilike multi-byte pattern cache |
Previous Message | Guillaume Smet | 2007-09-22 08:37:22 | Re: like/ilike improvements |