Horton
Menu

Re: Let's add a test for NLS translation of PRI* macros

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bryan Green <dbryan.green@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-12-09T18:24:11Z
Lists: pgsql-hackers 
I wrote:
> Hence, new version attached that just hard-codes es_ES.UTF-8.
> We'll see if cfbot agrees with my local testing.

Yay, that passed CI.  However, I fear this proves little about
what would happen on Windows with NLS enabled, because per the
other thread we don't have NLS enabled in the CI Windows builds.

AFAICS we don't have it enabled in any of the Windows buildfarm
animals either, which may well mean that I could push v6 and
the buildfarm would stay green.  I'm a bit tempted to do that
and see what happens.  I don't have any way to make further
progress on this question here.

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add a regression test to verify that NLS translation works.

  2. Support "j" length modifier in snprintf.c.