Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Lamar Owen writes:
Ok, let me repeat -- the '--enable-locale' setting will not affect the
collation sequence problem on RedHat. If you set PostgreSQL to use
locale, it uses it. If you configure PostgreSQL to not use locale, the
[EMAIL PROTECTED] (Trond Eivind GlomsrØd) writes:
Tom Lane [EMAIL PROTECTED] writes:
Also, since "LC_COLLATE=en_US" seems to misbehave rather spectacularly
on recent RedHat releases, I propose that initdb change "en_US" to "C"
if it finds that setting.
It does not misbehave in
Lamar Owen writes:
Yes, I want to ignore their default.
If you want to do that then the infinitely better solution is to compile
without locale support in the first place. (Make the locale-enabled
server a separate package.) Alternatively, the locale of the postgres
user to POSIX.
I can do
Peter Eisentraut wrote:
Lamar Owen writes:
Yes, I want to ignore their default.
If you want to do that then the infinitely better solution is to compile
without locale support in the first place. (Make the locale-enabled
server a separate package.) Alternatively, the locale of the
Lamar Owen writes:
Ok, let me repeat -- the '--enable-locale' setting will not affect the
collation sequence problem on RedHat. If you set PostgreSQL to use
locale, it uses it. If you configure PostgreSQL to not use locale, the
collation set by LANG, LC_ALL, or LC_COLLATE is _STILL_
Peter Eisentraut [EMAIL PROTECTED] writes:
Lamar Owen writes:
Ok, let me repeat -- the '--enable-locale' setting will not affect the
collation sequence problem on RedHat. If you set PostgreSQL to use
locale, it uses it. If you configure PostgreSQL to not use locale, the
collation set by
Peter Eisentraut [EMAIL PROTECTED] writes:
I have now received positive proof that en_US sort order on RedHat is
broken. For example, it asserts
'/root/' '/root0'
but
'/root/t' '/root0'
I defy you to find anyone in the US who will say that that is a
reasonable definition of string
Tom Lane wrote:
that contains only (or mostly) words like that. But I've got strong
doubts that the average user of a default RedHat installation expects
*all* data to get sorted that way, or that he wants us to honor a
default that he didn't ask for to the extent of disabling LIKE
Lamar Owen [EMAIL PROTECTED] writes:
I am not at all happy about the 'broken' RedHat locale -- the quick and
dirty solution is to remove or rename '/etc/sysconfig/i18n' -- but that
doesn't cure the root issue.
Actually, that suggestion points out that just nailing down LC_COLLATE
at initdb
Possible compromise: let initdb accept en_US, but have it spit out a
warning message:
NOTICE: initializing database with en_US collation order.
If you're not certain that's what you want, then it's probably not what
you want. We recommend you set LC_COLLATE to "C" and re-initdb.
For more
Tom Lane wrote:
Lamar Owen [EMAIL PROTECTED] writes:
Oh, and to make matters that much worse, on a RedHat system it doesn't
matter if you build with or without --enable-locale -- locale support is
in the libc used, and locale support gets used regardless of what you
select on the
Tom Lane writes:
Possible compromise: let initdb accept en_US, but have it spit out a
warning message:
NOTICE: initializing database with en_US collation order.
If you're not certain that's what you want, then it's probably not what
you want. We recommend you set LC_COLLATE to "C" and
Tom Lane wrote:
Lamar Owen [EMAIL PROTECTED] writes:
Collation was the same, regardless of the --enable-locale
setting. I got lots of 'bug' reports about the RPM's failing
Hmm. I reviewed that thread and found this comment from you:
: In a nutshell, yes. /etc/sysconfig/i18n on the
At 07:32 PM 11/24/00 -0500, Tom Lane wrote:
Possible compromise: let initdb accept en_US, but have it spit out a
warning message:
NOTICE: initializing database with en_US collation order.
If you're not certain that's what you want, then it's probably not what
you want. We recommend you set
Don Baccus [EMAIL PROTECTED] writes:
Are you SURE you want to use en_US collation? [no]
(ask the question, default to no?)
Yes, a question in initdb is ugly, this whole thing is ugly.
A question in initdb won't fly for RPM installations, since the RPMs
try to do initdb themselves (or am I
Tom Lane wrote:
Don Baccus [EMAIL PROTECTED] writes:
Are you SURE you want to use en_US collation? [no]
(ask the question, default to no?)
Yes, a question in initdb is ugly, this whole thing is ugly.
A question in initdb won't fly for RPM installations, since the RPMs
try to do
Lamar Owen [EMAIL PROTECTED] writes:
A command-line argument to initdb would suffice to override -- maybe a
'--initlocale' parameter??
Hardly need one, when setting LANG or LC_ALL will do just as well.
Now, what sort of default for --initlocale.
I think your complaints about RedHat's
Tom Lane wrote:
Lamar Owen [EMAIL PROTECTED] writes:
I think your complaints about RedHat's default are right back in your
lap ;-). Do you want to ignore their default, or not?
Yes, I want to ignore their default. This problem is more than just
cosmetic, thanks to the bugs that sparked this
18 matches
Mail list logo
