Re: Regex select ~ with ^ not using index on char field or text; Locale bug? - Mailing list pgsql-general

From Greg Maxwell
Subject Re: Regex select ~ with ^ not using index on char field or text; Locale bug?
Date
Msg-id Pine.GSO.3.96.1010430104952.25183D-100000@da1server
Whole thread Raw
In response to Regex select ~ with ^ not using index on char field or text; Locale bug?  (Greg Maxwell <gmaxwell@martin.fl.us>)
List pgsql-general
On Mon, 30 Apr 2001, Tom Lane wrote:

> Greg Maxwell  <gmaxwell@martin.fl.us> writes:
> > On performing queries such as select * from table where name ~ '^NAME.*';
> > the database fails to use the available Btree index where available, even
> > when the database is told not to use the SEQ_SCAN optimization.
>
> > PGsql was initlized and is started with the scripts in the RPM, so
> > LC_ALL=C is set.  PSQL is also run with LC_ALL=C.
>
> Are you *certain* the DB was initialized in locale C?  Try running
> contrib/pg_controldata to be sure.

If it wasn't, the start scripts in the RPM are broken.

Furthermore, I have reinited twice, very carefully and manually set all
the LC enviroment vars and still had the same result.

I wasn't aware of the pg_controldata program, I saw in other posts that
there was something in contrib to check this, but I couldn't find it.

Because of this, I changed the specfile to remove locale support, and
can't do further testing.. Sorry I didn't get your mail earlier.

Later this week, I'll be taking another system to RH7.1 + PG7.1, so I'll
let you know if I encounter the problem again.



pgsql-general by date:

Previous
From: Randall Perry
Date:
Subject: PHPPgAdmin or MS Access
Next
From: Tom Lane
Date:
Subject: Re: Regex select ~ with ^ not using index on char field or text; Locale bug?