Re: default locale considered harmful? (was Re: [GENERAL]

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: default locale considered harmful? (was Re: [GENERAL]
Date: 2003-06-02 02:32:12
Message-ID: 200306020232.h522WCG19699@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Our default indexes will be able to do =, >, <, ORDER BY, and the
> > special index will be able to do LIKE, ORDER BY, and maybe equals. Do I
> > have that correct?
>
> The default operator class supports comparisons (=, >, <, etc.) and ORDER
> BY based on those operators. The other operator class supports pattern
> matching operations (LIKE, SIMILAR, POSIX regexps).
>
> > Looking at CVS, I see the warning about non-C locales has been removed.
> > Should we instead mention the new LIKE index method?
>
> I don't see a need. The old warning was mainly because once you
> initdb'ed, you were basically stuck with your choice. Now we have plenty
> of options to query and adjust things later.

How are people going to know to use these special LIKE indexes?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-general by date

  From Date Subject
Next Message nolan 2003-06-02 03:04:41 Re: Advance Function
Previous Message Greg Sabino Mullane 2003-06-02 02:31:14 PGP / GnuPg signed checksums for PostgreSQL version 7.3.3

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-06-02 02:35:54 Re: compile error on cvs tip
Previous Message Christopher Kings-Lynne 2003-06-02 02:11:53 pg_database encoding again