RE: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607

Thanks, Tom. Is there any suggestion on how to track all the conversations in one thread? Seems like all our previous discussion are in different mail thread. It is not easy to track. 😊

Regards!
Haifang

-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Monday, June 3, 2024 3:55 PM
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Haifang Wang (Centific Technologies Inc) <v-haiwang(at)microsoft(dot)com>; Rahul Pandey <pandeyrah(at)microsoft(dot)com>; Vishwa Deepak <Vishwa(dot)Deepak(at)microsoft(dot)com>; Shawn Steele <Shawn(dot)Steele(at)microsoft(dot)com>; Amy Wishnousky <amyw(at)microsoft(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org; Shweta Gulati <gulatishweta(at)microsoft(dot)com>; Ashish Nawal <nawalashish(at)microsoft(dot)com>; Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607

Thomas Munro <thomas(dot)munro(at)gmail(dot)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