From: | carex(at)skynet(dot)be (carex) |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: select using regexp does not use indexscan |
Date: | 2004-11-15 17:12:30 |
Message-ID: | 3a0a211c.0411150912.414d1ecb@posting.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote in message news:<3972(dot)1100390524(at)sss(dot)pgh(dot)pa(dot)us>...
> Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> > On Tue, 9 Nov 2004, carex wrote:
> >> And it works also perfectly with Gentoo.
> >> So,is this a typical "Redhat Enterprise" problem ?
> >> Or do I overlook something ??
>
> > IIRC, in 7.3.x, index scans are only considered in "C" locale for
> > regexp/LIKE. In 7.4.x, non-"C" locale databases can use a special
> > index of a different opclass (<typename>_pattern_ops I believe).
>
> Not sure if this answer was explicit enough, so: evidently the database
> was initdb'd in "C" locale on Gentoo, but in some other locale on Red Hat.
> The only "typical Red Hat problem" is that they are more enthusiastic
> about setting up non-C default locales than some other distros.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
Thank you so much.
It is indeed clearer now.
So I did an initdb --locale=C -D /path/to/data
rebuild my database and started my "select" again.
I could see my index was used even when host~'^tna2';
Thanks again.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2004-11-16 06:52:22 | Re: Cascade updates wait until the end of the transaction? |
Previous Message | Theodore Petrosky | 2004-11-14 13:50:32 | Re: postgreSQL 8beta |