From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
cc: "Haifang Wang (Centific Technologies Inc)" <v-haiwang@microsoft.com>,
        Rahul Pandey <pandeyrah@microsoft.com>,
        Vishwa Deepak <Vishwa.Deepak@microsoft.com>,
        Shawn Steele <Shawn.Steele@microsoft.com>,
        Amy Wishnousky <amyw@microsoft.com>,
        "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>,
        Shweta Gulati <gulatishweta@microsoft.com>,
        Ashish Nawal <nawalashish@microsoft.com>,
        Magnus Hagander <magnus@hagander.net>
Subject: Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF #
 48475607
In-reply-to: 
 <CA+hUKGK-G=DB5MttZzzZf7mzTMxRVSACNg-WGK59Tk1Q9vY3cA@mail.gmail.com>
References: 
 <PH8PR21MB390263C479B81A1B7330E744E5182@PH8PR21MB3902.namprd21.prod.outlook.com>
 <PH8PR21MB3902F334A3174C54058F792CE5182@PH8PR21MB3902.namprd21.prod.outlook.com>
 <CA+hUKG+b_XqMZ6xkFhMCEwLXbGSN1rDYYY-En8MgFe81auRAAg@mail.gmail.com>
 <PH8PR21MB39022E5B54CE6E03E194B30FE5E22@PH8PR21MB3902.namprd21.prod.outlook.com>
 <CA+hUKGKrzGnCW3MoVC7gayHCtJQPEJKgpfQWD6c7eUvFp+ac+A@mail.gmail.com>
 <PH8PR21MB39027F1F4EAFEAE33EB4BA39E5E22@PH8PR21MB3902.namprd21.prod.outlook.com>
 <CA+hUKG+GUcSzk7UwvuLr4p84BQV8k2xvVAjToW=fQ5rCrciJ4A@mail.gmail.com>
 <872239.1715641638@sss.pgh.pa.us>
 <CA+hUKGJJgyc9xg+g_8_jPUV08Kr0NFdgq2_H9mm7-eZd7YVRQg@mail.gmail.com>
 <PH8PR21MB3902402C3C3C20DD8CB40AFFE5EC2@PH8PR21MB3902.namprd21.prod.outlook.com>
 <PH8PR21MB39027671C218DE448D8C091CE5EE2@PH8PR21MB3902.namprd21.prod.outlook.com>
 <CA+hUKG+oS+rriPvML+j6mZgCkJDsGP9bP7qopVxSLeTWsAOtsA@mail.gmail.com>
 <2682258.1716011233@sss.pgh.pa.us>
 <CA+hUKG+j5YwGtoV0_q3NxjD3EygxdwYeedUAFKamcLzR+PrcpQ@mail.gmail.com>
 <DS0PR21!
 MB390450195D21634ABCA26F4FE5E92@DS0PR21MB3904.namprd21.prod.outlook.com>
 <CA+hUKGJDv3pCnQXY13uYW1oe9CvFw8Y2j8mBMh2HGk_X0qYEcw@mail.gmail.com>
 <PH8PR21MB3902C3DB0535FD33CBF2E8C2E5E92@PH8PR21MB3902.namprd21.prod.outlook.com>
 <KL1P15301MB0387AF8D3B2FE878BF1B576AE3EA2@KL1P15301MB0387.APCP153.PROD.OUTLOOK.COM>
 <PSAP153MB0439B2D8386BDFF643A7B5A2BDEB2@PSAP153MB0439.APCP153.PROD.OUTLOOK.COM>
 <PH8PR21MB3902C9024782A8A3E26370ACE5F12@PH8PR21MB3902.namprd21.prod.outlook.com>
 <PH8PR21MB39022FCDB4806CD57694F50AE5FF2@PH8PR21MB3902.namprd21.prod.outlook.com>
 <CA+hUKGK-G=DB5MttZzzZf7mzTMxRVSACNg-WGK59Tk1Q9vY3cA@mail.gmail.com>
Comments: In-reply-to Thomas Munro <thomas.munro@gmail.com>
	message dated "Tue, 04 Jun 2024 09:22:22 +1200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <151228.1717455291.1@sss.pgh.pa.us>
Date: Mon, 03 Jun 2024 18:54:51 -0400
Message-ID: <151229.1717455291@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/151229.1717455291%40sss.pgh.pa.us>
Precedence: bulk

Thomas Munro <thomas.munro@gmail.com> writes:
> One open question is whether we should ship a translation file
> ourselves.  I have heard two opinions: Tom Lane proposed in this
> thread that there should be no file initially, we let the user figure
> out what to put in there.  Magnus Hagander proposed at the pgconf.dev
> conference last week that we should ideally ship a complete
> translation file and maintain it over time, and it should be installed
> not in pgdata but rather in the install directory.

FWIW, I'm kind of down on the latter approach, because I don't think
it'll move the needle very far.  Based on track record so far, there's
no chance that we will be aware of a Microsoft locale renaming before
it starts breaking users' databases.  Therefore, "edit the translation
file" is going to have to be a documented process in any case, because
affected users are not going to want to wait around for our next
release for a fix.  Also, if people do have to do that, it doesn't
seem like a great idea to tell them to modify an installed file rather
than a cluster-local configuration file.  What if they do a minor
version update but the minor version doesn't (yet) contain the fix?

Admittedly, the installed-file approach could make it more transparent
for people who'd done a PG minor update before the relevant Windows
update.  I'm not sure how large that set of people will be, though.

			regards, tom lane