| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LIKE indexing proposal |
| Date: | 2003-05-13 16:48:01 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961FAC@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> You've apparently forgotten all our previous history on that subject
> :-(. The above does not work in the presence of special sort rules for
> digraphs, etc. For example, that LIKE should certainly match ABCH ...
> but there are locales in which "CH" sorts after "D" and would not be
> found by an indexscan that runs from ABC to ABD.
Sorry, so is the start condition of >= 'ABC' also not valid ?
A new index scan method with the pattern as input would need to know when it can
safely stop (which is the problem I understand), but would have the advantage of
beeing able to filter unwanted tuples before the heap access.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-05-13 16:59:46 | Re: Scheduled jobs |
| Previous Message | Larry Rosenman | 2003-05-13 16:20:26 | Re: GUC and postgresql.conf docs |