Re: Repeatedly breaking indexes - SOLVED - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Repeatedly breaking indexes - SOLVED
Date
Msg-id 22441.1070292387@sss.pgh.pa.us
Whole thread Raw
In response to Re: Repeatedly breaking indexes - SOLVED  (Martin Edlman <edlman@fortech.cz>)
Responses Re: Repeatedly breaking indexes - SOLVED  (Martin Edlman <edlman@fortech.cz>)
List pgsql-bugs
Martin Edlman <edlman@fortech.cz> writes:
>     finally the problem is solved. The problem was with locales.

>     I installed and initialised the database under cs_CZ, so Pg
> recorded cs_CZ in all its configurations and startup scripts.
>     After that I changed /etc/sysconfig/i18n to use en_US locale as
> system default.
>     And that was the problem. According to "ps axe" the postmaster was
> running under en_US locales instead of cs_CZ as I expected.

"ps" is not a reliable guide to the locale settings being used by
Postgres.

The postmaster will adopt LC_COLLATE and LC_CTYPE from the settings
recorded in pg_control (by initdb) regardless of its environment.
Other, noncritical, settings such as LC_MESSAGES are taken from
postgresql.conf if specified there.  The environment values reported by
"ps" would only be used for noncritical settings, and then only if
not overridden by postgresql.conf.

So I'm not convinced that you've correctly identified the problem.
However, it seems possible that part of the issue is misbehavior if
the various LC_xxx settings aren't all alike --- could you dig further
and try to isolate it?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Martin Edlman
Date:
Subject: Re: Repeatedly breaking indexes - SOLVED
Next
From: SZUCS Gábor
Date:
Subject: Re: unix_socket_directory vs pg_ctl?