Re: OK, that's one LOCALE bug report too many...

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Don Baccus <dhogaza(at)pacifier(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OK, that's one LOCALE bug report too many...
Date: 2000-11-25 21:44:01
Message-ID: Pine.LNX.4.21.0011252233370.1028-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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_ honored, thanks
> to the libc used.

Well, I'm looking at Red Hat 7.0 here and the locale variables are most
certainly getting ignored in the default compile. Moreover, at no point
did strncmp() in glibc behave as you claim. You can look at it yourself
here:

http://subversions.gnu.org/cgi-bin/cvsweb/glibc/sysdeps/generic/strncmp.c

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-25 22:14:55 Re: OK, that's one LOCALE bug report too many...
Previous Message Joel Burton 2000-11-25 21:41:38 Warning: Don't delete those /tmp/.PGSQL.* files