| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Andrus <eetasoft(at)online(dot)ee> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Best way to use indexes for partial match at |
| Date: | 2005-11-09 21:05:03 |
| Message-ID: | 1131570303.3554.43.camel@state.g2switchworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2005-11-09 at 14:56, Andrus wrote:
> > you can create two indexes:
> >
> > CREATE INDEX myindex_lc on mytable(col1 text_pattern_ops);
> > and
> > CREATE INDEX myindex_normal ON foo(col1);
> >
> > the first one will be used when using LIKE and the other for normal
> > comparisons .
>
> Jaime,
>
> CREATE INDEX myindex_normal ON foo(col1);
>
> Creates btree structure. In other dbm system btree structure can be used for
> searches where only some first characters in index key are known.
>
> So I see no reason to create second index using text_pattern_ops for this
> purpose.
>
> I'm searching a way to use Postgres regular index for this.
Easy, do what those other databases do. Setup your database to not use
a locale.
initdb --locale=C
and you're golden.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-11-09 21:08:10 | Re: Best way to use indexes for partial match at beginning |
| Previous Message | Andrus | 2005-11-09 20:56:00 | Re: Best way to use indexes for partial match at beginning |