pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: tanseltekin01@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18425: KB5036892 Microsoft Update Package Issue
Date: Wed, 10 Apr 2024 16:30:29 +0200
Message-ID: <fecb14ee00e7d074d5ed3326c819a0ec6dd79e0b.camel@cybertec.at> (raw)
In-Reply-To: <18425-b471388573000d55@postgresql.org>
References: <18425-b471388573000d55@postgresql.org>

On Wed, 2024-04-10 at 10:06 +0000, PG Bug reporting form wrote:
> Operating system:   Windows 10
> 
> I am Mustafa from Turkiye, last night my computer is updated automatically.
> But KB50336892 number package file is stopped pgsql 11 service. I solved
> this problem form uninstalled this update package but. Windows 10 automatic
> update process will be updated other time. Please check this pgsql service
> and ıf it is required to contact to microsoft

This is the same problem as this one:
https://www.postgresql.org/message-id/flat/18196-b10f93dfbde3d7db%40postgresql.org

The problem is mostly in the Windows installer.

To fix your system, revert the patch so that you can start PostgreSQL
(you already did that).

Then stop the PostgreSQL service and take a backup of the data directory,
in case you mess up something below.  Start the service again.

Then you have to connect as superuser and manually update "pg_database" to
change the collation and character type to "tr-TR"; something like

  UPDATE pg_database
  SET datcollate = 'tr-TR.1254'
  WHERE datcollate = 'Turkish_Turkey.1254';

  UPDATE pg_database
  SET datctype = 'tr-TR.1254'
  WHERE datctype = 'Turkish_Turkey.1254';

(I don't have Windows - could somebody ascertain that these values are correct?)

Then you'd update "postgresql.conf" with a text editor and likewise change
all occurrences of "Turkish_Turkey.1254" to "tr-TR.1254".

After that, restart your PostgreSQL service and see if everything works as it should.

Then you should be able to apply the Windows patch, and PostgreSQL should be fine.

As I mentioned above, I don't run Windows myself, so try it on a test system before
you do it on the production database.

Yours,
Laurenz Albe





view thread (4+ messages)  latest in thread

Message-ID: <fecb14ee00e7d074d5ed3326c819a0ec6dd79e0b.camel@cybertec.at>
Permalink:  ../fecb14ee00e7d074d5ed3326c819a0ec6dd79e0b.camel@cybertec.at/
Also on:    postgresql.org/message-id/fecb14ee00e7d074d5ed3326c819a0ec6dd79e0b.camel@cybertec.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: laurenz.albe@cybertec.at, tanseltekin01@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18425: KB5036892 Microsoft Update Package Issue
  In-Reply-To: <fecb14ee00e7d074d5ed3326c819a0ec6dd79e0b.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox