Re: initdb --no-locale=C doesn't work as specified when the environment is not C - Mailing list pgsql-hackers

From Tom Lane
Subject Re: initdb --no-locale=C doesn't work as specified when the environment is not C
Date
Msg-id 1696010.1700669041@sss.pgh.pa.us
Whole thread Raw
In response to initdb --no-locale=C doesn't work as specified when the environment is not C  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: initdb --no-locale=C doesn't work as specified when the environment is not C
List pgsql-hackers
Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> Commit 3e51b278db leaves lc_* conf lines as commented-out when
> their value is "C". This leads to the following behavior.

Hmm ... I see a contributing factor here: this bit in
postgresql.conf.sample is a lie:

#lc_messages = 'C'            # locale for system error message
                    # strings

A look in guc_tables.c shows that the actual default is '' (empty
string), which means "use the environment", and that matches how the
variable is documented in config.sgml.  Somebody --- quite possibly me
--- was misled by the contents of postgresql.conf.sample into thinking
that the lc_xxx GUCs all default to C, when that's only true for the
others.

I think that a more correct fix for this would treat lc_messages
differently from the other lc_xxx GUCs.  Maybe just eliminate the
hack about not substituting "C" for that one?

In any case, we need to fix this mistake in postgresql.conf.sample.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Adding facility for injection points (or probe points?) for more advanced tests
Next
From: Maxim Orlov
Date:
Subject: How to stop autovacuum silently