Re: Adding NetBSD and OpenBSD to Postgres CI - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Adding NetBSD and OpenBSD to Postgres CI
Date
Msg-id 2352043.1734457486@sss.pgh.pa.us
Whole thread Raw
In response to Re: Adding NetBSD and OpenBSD to Postgres CI  (Andres Freund <andres@anarazel.de>)
Responses Re: Adding NetBSD and OpenBSD to Postgres CI
Re: Adding NetBSD and OpenBSD to Postgres CI
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2024-11-12 11:38:11 +0300, Nazir Bilal Yavuz wrote:
>> It was because initdb was failing on NetBSD when the LANG and LC_ALL
>> is not set to C. I rephrased the comment and moved this under NetBSD
>> task.

> Do you happen to have a reference to the failure?  The environment variables +
> the exact error message would be good.  Kinda feels like that shouldn't
> happen with a default netbsd install.

On mamba's host (pretty vanilla NetBSD 10.0):

$ env | grep ^L
LOGNAME=tgl
$ LANG=C initdb
... works fine ...
$ rm -rf $PGDATA
$ locale -a | grep en_US
en_US.ISO8859-1
en_US.ISO8859-15
en_US.US-ASCII
en_US.UTF-8
$ LANG=en_US.UTF-8 initdb
The files belonging to this database system will be owned by user "tgl".
This user must also own the server process.

initdb: error: invalid locale settings; check LANG and LC_* environment variables


I seem to recall noticing this when I was setting up mamba, but
I didn't feel like pursuing it so I just set the animal to test
only C locale.

> Was about to apply that, but then started to wonder if we don't need the same
> for configure? And it sure looks like that has the same problem?
> Which also confuses me some, at some point this presumably worked?

The configure path does work on NetBSD 10, and has for some time.
I've never tested it with meson though.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON json_table plan clause
Next
From: Andrew Dunstan
Date:
Subject: Re: Standardizing the file header?