BUG #18196: Databases Created in Turkish Language Will Not Run on the Latest Version of Windows

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: halilhanbadem(at)gmail(dot)com
Subject: BUG #18196: Databases Created in Turkish Language Will Not Run on the Latest Version of Windows
Date: 2023-11-15 09:04:28
Message-ID: 18196-b10f93dfbde3d7db@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18196
Logged by: Halil Han Badem
Email address: halilhanbadem(at)gmail(dot)com
PostgreSQL version: 15.4
Operating system: Windows 11 22H2 22621.2715
Description:

Hello,

This morning, I noticed that my computer at the office and my computer at
home had received automatic updates. Subsequently, I received reports of
some errors. Upon investigation, I found that the PostgreSQL service was not
running, and the error indicated that it was due to a problem in the
postgresql.conf file. After extensive research, I discovered that in the
Windows 11 22H2 22621.2715 update, the term "Turkey" had been changed to
"Türkiye." As a result, Turkish_Turkey.1254 is no longer present in the
operating system. Instead of Turkish_Turkey.1254, the Windows system now
uses Turkish_Türkiye.1254.

Databases created with Turkish_Turkey.1254 cannot find the corresponding
locale, resulting in errors and service disruptions. After a fresh
installation, I observed the following expressions in the postgresql.conf
file.

# These settings are initialized by initdb, but they can be changed.
lc_messages = 'Turkish_Türkiye.1254' # locale for system error message
# strings
lc_monetary = 'Turkish_Türkiye.1254' # locale for monetary formatting
lc_numeric = 'Turkish_Türkiye.1254' # locale for number formatting
lc_time = 'Turkish_Türkiye.1254' # locale for time formatting

Therefore, there is a conflict, and I request your assistance in addressing
this matter.

Thank you,
Best regards.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-11-15 09:58:56 BUG #18198: Constantly getting errors
Previous Message Pavel Stehule 2023-11-15 07:52:53 Re: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement