| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Wes <wespvp(at)syntegra(dot)com> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Leading substrings - alternatives with 8.1.3? |
| Date: | 2006-05-01 21:05:28 |
| Message-ID: | 20060501210528.GC27150@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 01, 2006 at 01:45:35PM -0500, Wes wrote:
> On 5/1/06 12:47 PM, "Martijn van Oosterhout" <kleptog(at)svana(dot)org> wrote:
>
> > Check the documentation, but if you declare a index with (for example)
> > text_pettern_ops, then LIKE will work even if the rest of your DB is
> > UTF-8.
>
> My understanding of using operator classes is that I'd have to create two
> indexes for each column - one with and one without the operator class. That
> is also what was indicated in the original thread. Defining multiple
> indexes on a given column isn't feasible, due to the database size (100
> million rows per day).
Oh right. If you want ordinary <,=,> to work for utf-8 and be indexed,
you need to have both. OTOH, if you're happy with text_pattern_ops for
ordinary lookups, you can use ~<~, ~=~, ~>~ to use the that index for
matches..
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John D. Burger | 2006-05-01 21:23:41 | Re: How would I write this query... |
| Previous Message | EbGrooveCb | 2006-05-01 20:16:15 | Using the REPLACE command to replace all vowels |