Re: Solaris versus our NLS files

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Nico Williams <nico(at)cryptonector(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Solaris versus our NLS files
Date: 2025-12-09 23:36:19
Message-ID: 308000.1765323379@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Wed, Dec 10, 2025 at 11:22 AM Nico Williams <nico(at)cryptonector(dot)com> wrote:
>> How about supporting only UTF-8 locales?

> Yeah, if nobody noticed this wasn't working at all, then it makes
> sense to defer the generation of .mo files for non-UTF-8 codesets
> until someone eventually does notice that it still doesn't work in
> legacy locales and feels inclined to do something about it, ie
> forever. Tom's goal of having basic tests pass will be satisfied by
> UTF-8-only.

Right. For the moment I only care about verifying that (a) some
translation happens and (b) the PRI* macros work as-expected.
Since we've already discovered platform-specific failures on both
points, this seems like a very worthwhile exercise.

Encoding-specific behaviors might be worth testing later, but
I'm not excited about that personally.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2025-12-09 23:54:00 Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
Previous Message Matthias van de Meent 2025-12-09 23:33:23 Small bugs regarding resowner handling in aio.c, catcache.c