Re: LC_COLLATE=C not working - Mailing list pgsql-general

From Robert Wille
Subject Re: LC_COLLATE=C not working
Date
Msg-id 3a3101c389c8$7a973420$6402a8c0@zucchini
Whole thread Raw
In response to Re: LC_COLLATE=C not working  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
pg_controldata $PGDATA says LC_COLLATE=C
pg_controldata $PGDATA/data says LC_COLLATE=en_US.iso885915

Perhaps this is a related problem. When I run dbinit, it puts a bunch of
configuration stuff in $PGDATA. When I start the postmaster, it tells me it
is initializing the database and creates $PGDATA/data and puts the same
configuration stuff there. I have no idea why it creates two sets of
configuration data. I don't see this on my test server, just on my
production server. My guess is that when it initializes the database when
the postmaster starts, that it isn't getting the LC_COLLATE setting.

----- Original Message -----
From: "Tom Lane tgl-at-sss.pgh.pa.us |Postgres|"
<xf54hm6pap0t@sneakemail.com>
To: "Robert Wille" <robertw@willeweb.com>
Cc: "Peter Eisentraut peter_e-at-gmx.net |Postgres|"
<4628hm6fbl0t@sneakemail.com>; <pgsql-general@postgresql.org>
Sent: Friday, October 03, 2003 9:35 AM
Subject: Re: [GENERAL] LC_COLLATE=C not working


> "Robert Wille" <vmg2rad02@sneakemail.com> writes:
> >> You probably still have LC_ALL set to something else.  LC_ALL overrides
> >> LC_COLLATE and friends, which in turn override LANG.
>
> > Nope. Any other ideas?
>
> Please use pg_controldata to verify the LC_ settings on both databases.
> I suspect they are not really both C.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
>                http://archives.postgresql.org


pgsql-general by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: updating records
Next
From: Tom Lane
Date:
Subject: Re: Query FKey Constraint Table and Column Names