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

From Andres Freund
Subject Re: Adding NetBSD and OpenBSD to Postgres CI
Date
Msg-id kccyyxtzbb4dihtjs3bphkfuogzymffxk5rzvzryjiectyvpqe@lsn7o7l5spps
Whole thread Raw
In response to Re: Adding NetBSD and OpenBSD to Postgres CI  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Adding NetBSD and OpenBSD to Postgres CI
List pgsql-hackers
Hi,

On 2024-12-17 12:44:46 -0500, Tom Lane wrote:
> 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.

Heh, I guess that's good enough for CI then too :)

It'd be helpful if the error message ought to at least include the category
being tested, perhaps it's just one category failing or such?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Maybe we should reduce SKIP_PAGES_THRESHOLD a bit?
Next
From: Andres Freund
Date:
Subject: Re: Adding NetBSD and OpenBSD to Postgres CI