Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607
Tom Lane <tgl@sss.pgh.pa.us>
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>
Date: 2024-06-03T22:54:51Z
Lists: pgsql-bugs
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Reject non-ASCII locale names.
- ce17de580f90 16.5 landed
- 9c7acc33307b 17.1 landed
- adbb27ac89e0 18.0 landed
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