Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVz9R-00CebP-Tn for pgsql-general@arkaria.postgresql.org; Mon, 22 Jul 2024 19:56:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sVz9Q-006NXG-1B for pgsql-general@arkaria.postgresql.org; Mon, 22 Jul 2024 19:56:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVz9O-006NX7-O4 for pgsql-general@lists.postgresql.org; Mon, 22 Jul 2024 19:56:51 +0000 Received: from fout6-smtp.messagingengine.com ([103.168.172.149]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVz9K-000uti-HV for pgsql-general@lists.postgresql.org; Mon, 22 Jul 2024 19:56:49 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 4FE8D13801B9; Mon, 22 Jul 2024 15:56:42 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 22 Jul 2024 15:56:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1721678202; x=1721764602; bh=qL8DzbHpYsj4tbeC/QNqJ3Sb4/hsec/Hg5b6JZkBnyc=; b= f3+FVBngtejLqhmj9XYliWVkX8+1KhGCWJxIb+KhftU5Bcrd95gvj/i8h0xsBOKX oSE+NXvKMkm2n/SG4kj0e9+2KXVmGwWCx57e5SXCHSs+DHNnb+lGPGVzc7Iucwxf oW4FtVDwc5dTNmRDbCYnLZemXzOYwUUaz7Rsb09hFMyTexxBICocf1v+ehqHJIBU WXR78T/bRRBpTJmaeopRhFaAby/IhY7unZ+nCW+HePmIAsSFkKCbqWiQiGoOXtDl 16NGo3NCVqb0uHAw3PGcLG2AXNwfQJ++xORChQNsGoGXmBxYK2SYMc3pHcYA6bL1 XN3bhcNA8Ncb7GDUlUUZ8Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1721678202; x= 1721764602; bh=qL8DzbHpYsj4tbeC/QNqJ3Sb4/hsec/Hg5b6JZkBnyc=; b=q QyJl5TycRcZMFfcJH62E6fDJTEQBW4Cja7dHSSPwPFwh0xwvr39Z1/yZu8w/glnN Tsi3xsbqndcrcy81QtvlxhMRNJeGTBSR4ZWeKfBUOs0Lk5c46a9xYSTBnJcHHT5j paW25w2LNrsYTuzYHkl8uhRNsFjoZCXEz1qsf6FYNW3dN9i/xnc47tbDV1FVoWRs Q8FxnJ7sD8VZF8U3IB/1XTnv6a5aYtbRf7VXZNdJ1POmIbY0TO3iP2tao6PsuEpn bRAtk9O78ezlteraBqC9JRx1eRBO/8lFvGX5xHo2L4A/oGyQCQTDHmvx1Yah/xwT jqNdO5JRqcllPbA2C4kCA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrheejgddugeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepveffkeekfeduvdehfeegkefhfeegjeduiedvfeej iefhteduvdfggeeiuedtfedunecuffhomhgrihhnpehmihgtrhhoshhofhhtrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 22 Jul 2024 15:56:41 -0400 (EDT) Message-ID: <88e330d0-907b-404c-9ec4-4d8a58bbb1a2@aklaver.com> Date: Mon, 22 Jul 2024 12:56:39 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Windows installation problem at post-install step To: =?UTF-8?B?RXJ0YW4gS8O8w6fDvGtvZ2x1?= Cc: pgsql-general@lists.postgresql.org References: <44b44ece-dce6-4b4f-b751-8787a5a071e0@aklaver.com> <011a5254-4abb-460b-bd02-92e8dfc0e5ea@aklaver.com> <9cc12221-ba75-4ba0-803f-51be5c8f1525@aklaver.com> <4c21a115-ec58-4e79-86b8-8626bd307e02@aklaver.com> <34aefaae-7c57-4593-af82-8c83eb31f3ec@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/22/24 11:48, Ertan Küçükoglu wrote: > Adrian Klaver >, 22 Tem 2024 Pzt, 21:10 tarihinde > şunu yazdı: > > I am getting out of my depth here, but I am pretty sure that: > > ENCODING = 'UTF8' LOCALE_PROVIDER = libc LOCALE = 'Turkish_Turkey.1254' > > is not going to work. That you will need to change the locale to a > Turkish UTF8 name. > > > I added tr_TR.UTF-8 to the system locales. > I also changed all Turkish_Turkey.1254 to tr_TR.UTF-8 in the dump file. > Unfortunately, I found that there are some databases created using > WIN1254 encoding. > I do not know what I should do with them. I don't think simply changing > WIN1254 -> UTF8 will work. > I will probably wait for a working Windows installer. From previous post of yours: "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=41158 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." Why not use that? > > Thanks & Regards, > Ertan -- Adrian Klaver adrian.klaver@aklaver.com