BUG #18136: lc_messages is the empty string but should be 'C'?

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: gavinpanella(at)gmail(dot)com
Subject: BUG #18136: lc_messages is the empty string but should be 'C'?
Date: 2023-09-27 15:04:55
Message-ID: 18136-4914128da6cfc502@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18136
Logged by: Gavin Panella
Email address: gavinpanella(at)gmail(dot)com
PostgreSQL version: 16.0
Operating system: macOS
Description:

Given a server:

```
initdb -D foo --locale=C
pg_ctl start -D foo -l logfile -w -o "-h '' -k $PWD/foo"
```

In PostgreSQL 16.0 the value of lc_messages is the empty string.

But in PostgreSQL from 9.x through to 15.x the value of lc_messages is
'C'.

I have tried using `initdb ... --lc-messages=C` and `LC_MESSAGES=C pg_ctl
start ...` and `LC_MESSAGES=C psql ...` with the same result.

However, if I run initdb with a locale other than C, e.g. POSIX or fr_FR,
then the value of lc_messages *does* reflect my choice.

Using --lc-messages with initdb also sets lc_messages as expected.

(This is something I observed from some test suites I run, and I dug into it
to see if there was a problem. Other than needing me to update those tests,
it is not affecting me at present.)

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyle MacMillan 2023-09-27 19:26:09 Re: md5 password valid and invalid after upgrading
Previous Message Japin Li 2023-09-27 14:16:47 Re: Bug of psql meta-command \sf & \sv