Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607
John McKown <john.archie.mckown@gmail.com>
From: John McKown <john.archie.mckown@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>, "Haifang Wang (Centific Technologies Inc)" <v-haiwang@microsoft.com>,
pgsql-bugs@lists.postgresql.org
Date: 2024-05-13T23:09:52Z
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
Just curious. Why a plain text file rather than a system table? On Mon, May 13, 2024, 18:07 Tom Lane <tgl@sss.pgh.pa.us> wrote: > Thomas Munro <thomas.munro@gmail.com> writes: > > Longer term I'm looking for something better than that though, because > > it doesn't address the root cause (need for stable identifiers), and > > will only ever allow us to fix problems with the old unstable names > > *after* users complain that their database is dead, 3-6 months after > > in fact due to release cycles. I think a dynamic mapping file might > > be better? (Maybe win32locale.c should be able to read that kludge > > table from a file that you can give it with an environment variable, > > or something like that?) > > +1 for the long-term solution being more-stable locale identifiers. > However, we should try to build something that will let users get > out of these situations with the existing identifiers, so I like > your idea of a plain-text mapping file for Windows locale names. > I don't think an environment variable is necessary; just define > a fixed name "$PGDATA/locale_map.txt" or such. If that file > exists, just read it and map the pg_database field values with it. > > Maybe this shouldn't even be Windows-specific? Are there any > cases where it'd save people's bacon on other platforms? > > regards, tom lane > > >