MIME-Version: 1.0
References: <CAH2i4ydECHZPxEBB7gtRG3vROv7a0d3tqAFXzcJWQ9hRsc1znQ@mail.gmail.com>
 <80c9b0ea-c874-40ad-a006-fb1eb37464c2@aklaver.com> <CAH2i4yfkH7YPoLz1aE6MQiBOm8dra5uOTpn51=9ce_Tm6fy3Pw@mail.gmail.com>
 <a9c619c4-f681-4e28-b1d0-cb4845e06fe8@aklaver.com> <CAH2i4ycV8p_uDsdGRcP3bWcU52ogojg9_-mT8uMixSqpNmW7Sg@mail.gmail.com>
 <d55c35b9-a658-4961-849e-871e7dd23fe9@aklaver.com> <CAH2i4yfBEYmOzsvsT=D+ySpLpsEW2O1VfUwx9Ckd69du67YY_w@mail.gmail.com>
 <44b44ece-dce6-4b4f-b751-8787a5a071e0@aklaver.com> <CA+hUKGJA4pGEeZtfUUEuQmNNO7x16wZ+RWOeXP+tq3Hf4iu8oQ@mail.gmail.com>
In-Reply-To: <CA+hUKGJA4pGEeZtfUUEuQmNNO7x16wZ+RWOeXP+tq3Hf4iu8oQ@mail.gmail.com>
From: =?UTF-8?B?RXJ0YW4gS8O8w6fDvGtvZ2x1?= <ertan.kucukoglu@gmail.com>
Date: Mon, 22 Jul 2024 02:58:11 +0300
Message-ID: <CAH2i4yeMK=q3a_+N8hLC8HuToPCNtgk=v0SwDv99WHQ4k5=vrA@mail.gmail.com>
Subject: Re: Windows installation problem at post-install step
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>, pgsql-general@lists.postgresql.org, 
	Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
Content-Type: multipart/alternative; boundary="00000000000011b2b1061dcab44c"
Archived-At: <https://www.postgresql.org/message-id/CAH2i4yeMK%3Dq3a_%2BN8hLC8HuToPCNtgk%3Dv0SwDv99WHQ4k5%3DvrA%40mail.gmail.com>
Precedence: bulk

--00000000000011b2b1061dcab44c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thomas Munro <thomas.munro@gmail.com>, 21 Tem 2024 Paz, 23:27 tarihinde
=C5=9Funu yazd=C4=B1:

> I guess this is where EDB installer issues should go:
>
> https://github.com/EnterpriseDB/edb-installers/issues


Thanks. I just added a new issue there.

2.  Some existing database clusters which had been installed with the
> name "Turkish_Turkey.1254" became unstartable when the OS upgrade
> renamed that locale to "Turkish_T=C3=BCrkiye.1254".  I'm trying to provid=
e
> a pathway[2] to fix such systems in core PostgreSQL in the next minor
> release.  Everyone affected probably already found another way but at
> least next time a country is renamed this might help with the next
> point too.
>

I was also hit by that OS update.
There is a Microsoft tool for creating a locale installer
https://www.microsoft.com/en-us/download/details.aspx?id=3D41158
Using that tool and adding a second locale Turkish_Turkey.1254 (name before
Microsoft update) in the OS can fix your broken PostgreSQL.
I believe most people simply choose this path.
There are also several blogs/articles written in Turkish about the problem.

3.  I'd also like to teach initdb to use BCP47 names like "tr-TR"
> instead of those names by default (ie if you don't specify a locale
> name explicitly), and have proposed that before[3] but it hasn't gone
> in due to lack of testing/reviews from Windows users.  It seems like
> that doesn't matter much in practice to all the people using the
> popular EDB installer, since it apparently takes control of picking
> the locale and explicitly passes it in (and screws up the encoding as
> we have now learned).
>

If I am not mistaken BCP47 names are already used in Linux systems.
Using them would make PostgreSQL use the same locale names across Linux and
Windows systems.
I can help with the testing part. Let me know the details, please.

Thanks & Regards,
Ertan

--00000000000011b2b1061dcab44c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Thomas Munro &lt;<a href=3D"mailto:thomas=
.munro@gmail.com">thomas.munro@gmail.com</a>&gt;, 21 Tem 2024 Paz, 23:27 ta=
rihinde =C5=9Funu yazd=C4=B1:<br></div><div class=3D"gmail_quote"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">I guess this is where EDB installe=
r issues should go:<br>
<br>
<a href=3D"https://github.com/EnterpriseDB/edb-installers/issues" rel=3D"no=
referrer" target=3D"_blank">https://github.com/EnterpriseDB/edb-installers/=
issues</a></blockquote><div><br></div><div>Thanks. I just added a new issue=
 there.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">2.=C2=A0 Some existing database clusters which had been installed with t=
he<br>
name &quot;Turkish_Turkey.1254&quot; became unstartable when the OS upgrade=
<br>
renamed that locale to &quot;Turkish_T=C3=BCrkiye.1254&quot;.=C2=A0 I&#39;m=
 trying to provide<br>
a pathway[2] to fix such systems in core PostgreSQL in the next minor<br>
release.=C2=A0 Everyone affected probably already found another way but at<=
br>
least next time a country is renamed this might help with the next<br>
point too.<br></blockquote><div><br></div><div>I was also hit by that OS up=
date.</div><div>There is a Microsoft tool for creating a locale installer=
=C2=A0</div><div><a href=3D"https://www.microsoft.com/en-us/download/detail=
s.aspx?id=3D41158">https://www.microsoft.com/en-us/download/details.aspx?id=
=3D41158</a>=C2=A0</div><div>Using that tool and adding a second locale Tur=
kish_Turkey.1254 (name before Microsoft update) in the OS can fix your brok=
en PostgreSQL.</div><div>I believe most people simply choose this path.</di=
v><div>There are also several blogs/articles written in Turkish about the p=
roblem.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
3.=C2=A0 I&#39;d also like to teach initdb to use BCP47 names like &quot;tr=
-TR&quot;<br>
instead of those names by default (ie if you don&#39;t specify a locale<br>
name explicitly), and have proposed that before[3] but it hasn&#39;t gone<b=
r>
in due to lack of testing/reviews from Windows users.=C2=A0 It seems like<b=
r>
that doesn&#39;t matter much in practice to all the people using the<br>
popular EDB installer, since it apparently takes control of picking<br>
the locale and explicitly passes it in (and screws up the encoding as<br>
we have now learned).<br></blockquote><div><br></div><div>If I am not mista=
ken BCP47 names are already used in Linux systems.</div><div>Using them wou=
ld make PostgreSQL use the same locale names across Linux and Windows syste=
ms.</div><div>I can help with the testing part. Let me know the details, pl=
ease.</div><div><br></div><div>Thanks &amp; Regards,</div><div>Ertan</div><=
/div></div>

--00000000000011b2b1061dcab44c--