From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: halilhanbadem@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18196: Databases Created in Turkish Language Will Not Run on
 the Latest Version of Windows
In-reply-to: <f41b857b00c92254e55a0e3486d76ad7ae1bde18.camel@cybertec.at>
References: <18196-b10f93dfbde3d7db@postgresql.org>
 <f41b857b00c92254e55a0e3486d76ad7ae1bde18.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Wed, 15 Nov 2023 18:48:47 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2694194.1700072765.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Wed, 15 Nov 2023 13:26:05 -0500
Message-ID: <2694195.1700072765@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2694195.1700072765%40sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> On Wed, 2023-11-15 at 09:04 +0000, PG Bug reporting form wrote:
>> [ Microsoft decided to rename their Turkish locales ]

> This seems to be a really nasty problem that Microsoft has created for us.
> Even if the server started, you could not connect to the database if the
> collation persisted in pg_database is no longer accepted by the operating
> system.

Yeah, that's a mess.  The postgresql.conf entries could be fixed by hand,
but if you've got "Turkish_Turkey.1254" in pg_database.datcollate or
datctype then there's no easy way around that.

I think really the right fix is a whole bunch of WTFs directed at
Microsoft.  I can understand wanting to support the Turkish_Türkiye
spelling, but not having a backward-compatibility entry for the old
spelling is a colossal blunder -- especially in a minor OS release.
Aren't these the same people who prize backward compatibility at
any cost?

			regards, tom lane