Re: like/ilike improvements

Guillaume Smet <guillaume.smet@gmail.com>

From: "Guillaume Smet" <guillaume.smet@gmail.com>
To: "Gregory Stark" <stark@enterprisedb.com>
Cc: "ITAGAKI Takahiro" <itagaki.takahiro@oss.ntt.co.jp>, "Andrew Dunstan" <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2007-09-21T17:12:05Z
Lists: pgsql-hackers
Gregory,

On 9/21/07, Gregory Stark <stark@enterprisedb.com> wrote:
> Hm, it does seem I missed like.c when I converted all the text operators to
> avoid detoasting packed varlenas. I'll send a patch in a few minutes to do
> that. I'm surprised it would have such a large effect though.

The patch doesn't seem to apply cleanly on head (I have a problem with
oracle_compat.c). I tested it though with latin1 encoding.

The LIKE case is better:
cityvox_latin1=# SELECT e.numeve FROM evenement e WHERE e.libgeseve
LIKE '%hocus pocus%';
 numeve
--------
(0 rows)

Time: 98.995 ms

-> it seems to be as fast as 8.2 was, now.

The ILIKE case seems to go into an infinite loop: postmaster takes
100% of CPU and the query never finishes.

--
Guillaume