Re: strange problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Böhm, Sebastian (Vendor)" <sebastian(dot)boehm(at)friendscout24(dot)de>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: strange problem
Date: 2002-12-19 00:16:08
Message-ID: 13380.1040256968@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?iso-8859-1?Q?=22B=F6hm=2C_Sebastian_=28Vendor=29=22?= <sebastian(dot)boehm(at)friendscout24(dot)de> writes:
> I installed an newer rpm of the glibc (2.2.2-8.1 / 2.2.2-4 before) und
> reinitialized the database with locale=3DC.

> Just after installing the rpm, the problem was still there (reindex I =
> did),
> but after dump/initdb --locale=3DC/import the problem was gone.
> Dont know wheater it is the reinit with new glibc or the reinit with
> locale=3DC, dont have the time to figure it out.

If I am correct in guessing that strcoll is to blame, then setting the
locale to C would have made the problem go away. I am dubious that
glibc 2.2.2-8 fixes the strcoll bug --- the notes I have say that that
fix appeared in glibc 2.2.3. However, if you're happy running in C
locale then it doesn't really matter whether strcoll works or not ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Böhm, Sebastian (Vendor) 2002-12-19 00:18:13 Re: strange problem
Previous Message Tom Lane 2002-12-18 19:17:47 Re: strange problem