| From: | Jules Bean <jules(at)jellybean(dot)co(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Yet another LIKE-indexing scheme |
| Date: | 2000-09-06 08:49:14 |
| Message-ID: | 20000906094914.B31824@grommit.office.vi.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 02, 2000 at 01:39:47PM -0400, Tom Lane wrote:
> > So what happens with "WHERE name like 'Czec%`" ?
>
> Our existing code fails because it generates WHERE name >= 'Czec' AND
> name < 'Czed'; it will therefore not find names beginning 'Czech'
> because those are in another part of the index, between 'Czeh' and
> 'Czei'. But WHERE name >= 'Cze' AND name < 'Czf' would work.
(OK, I haven't read the previous discussion. Guilty, m'lud)
Why should it? If 'ch' is one letter, then surely 'czech' isn't LIKE
'czec%'. Because 'czec%' has a second c, wheres, 'czech' only has one
'c' and one 'ch'?
Jules
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Raschepkin | 2000-09-06 13:59:10 | Re: WAL |
| Previous Message | Tatsuo Ishii | 2000-09-06 08:17:06 | Re: [PATCHES] Important 7.0.* fix to ensure buffers are released |