Horton

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

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: "Haifang Wang (Centific Technologies Inc)" <v-haiwang@microsoft.com>, Thomas Munro <thomas.munro@gmail.com>, Rahul Pandey <pandeyrah@microsoft.com>, Shawn Steele <Shawn.Steele@microsoft.com>
Cc: Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>, Vishwa Deepak <Vishwa.Deepak@microsoft.com>, Amy Wishnousky <amyw@microsoft.com>, Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, Shweta Gulati <gulatishweta@microsoft.com>, Ashish Nawal <nawalashish@microsoft.com>
Date: 2024-08-29T21:09:37Z
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 →

  1. Reject non-ASCII locale names.

On 2024-08-29 Th 1:53 PM, Haifang Wang (Centific Technologies Inc) wrote:
> Thanks for the reply, Andrew and Thomas. The issue is originally from user feedback. And our team verified and reproduced it too. And it is high priority from our end is because: 1. It is regression, it did not see it in the previous build. 2. After the crash happened, even the app could be installed, but cluster initialization failed. And due to which we cannot connect to the database and proceed further.


Please don't top-post on PostgreSQL lists.


If I read Thomas correctly, the solution is to create a locale with an 
acceptable (pure Ascii) name using Locale Builder, and then call initdb 
using that name. It might be that you need to do some of this manually 
if the installer fails. IIRC is it possible to run the installer without 
having it create a cluster automatically. You can then set up the 
cluster and create a windows service manually using initdb / pg_ctl.


cheers


andrew



--
Andrew Dunstan
EDB: https://www.enterprisedb.com