Обсуждение: Re: BUG #18098: Console code page issue Postgresql 14.7

The following bug has been logged on the website:

Bug reference:      18098
Logged by:          Gokul
Email address:      gokulkrishnan99102@gmail.com
PostgreSQL version: 14.7
Operating system:   Windows 10 Pro, Version - 22H2
Description:       

Hi Team,
          We are facing an issue on executing initdb.exe  it throws error
like 'initdb: error: The program "postgres" was found by
"pgsql\bin\initdb.exe" but was not the same version as initdb'.
          But postgres.exe and initdb.exe version are same. After referring
many articles, sites in google. We came to know that Console code page
causes this issue on specific case. If we are setting console code page on
particular cmd session it won't affects the init db process. But if chcp
value entry present in registry at the path
"HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\Autorun"(This entry
helps to execute any command in cmd at the time of opening). Hence in the
entire initdb process if cmd inkoved internally this chcp values will be set
on each cmd session. This may cause encoding issue during initdb process. On
referring postgres forum we found an bug raised with exact senario in
postgres 11 but no response found for that mail thread. Kindly help us to
resolve this issue.
         Refer this link(bug) ->
https://www.postgresql.org/message-id/15856-97c7d2fd3b86f13d@postgresql.org

On Fri, 2023-09-08 at 12:02 +0530, Gokul Krishnan wrote:
> Kindly provide the solution accordingly.

Kindly provide a good problem description.  Don't say "I run initdb.exe",
tell us how exactly you ran it, and what you ran before that to provoke the error.
What was your OS locale at that time? What was the exact error message?
What exactly did you have to change in the registry to make the problem go away?

Yours,
Laurenz Albe

Hi Laurenz,

        Apologies for the inconvenience,I have shared the detailed description below. Kindly provide a solution for this issue.

I have tried to initialize data directory using this below command,

initdb.exe -D "..\data" -U postgres --no-locale -E UTF8

Exact error returned by postgres,

initdb: error: The program "postgres" was found by "E:\pgsql\bin/initdb.exe"
but was not the same version as initdb.
Check your installation.

I have tried with different chcp values(1252,437.. etc) that are supported by postgres but doesn't work for my case(encoding command also changed according to registry chcp value) .If I remove the Active code page : 65001 from the registry editor, then the above mentioned initdb command executes successfully.

Successful execution log for your reference,

Microsoft Windows [Version 10.0.19045.3324]
(c) Microsoft Corporation. All rights reserved.

E:\pgsql\bin>initdb.exe -D "..\data" -U postgres --no-locale -E UTF8
The files belonging to this database system will be owned by user "gokul".

This user must also own the server process.

The database cluster will be initialized with locale "C".
The default text search configuration will be set to "english".

Data page checksums are disabled.

creating directory ../data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... windows
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Asia/Calcutta
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D ^"^.^.^\data^" -l logfile start

 Registry Editor key I have removed,

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\Autorun  -> Removed the Value data(chcp 65001) content.

My Current System locale is English (United States)

Thanks & Regards,

 Gokul

On Fri, Sep 8, 2023 at 12:17 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:

On Fri, 2023-09-08 at 12:02 +0530, Gokul Krishnan wrote:
> Kindly provide the solution accordingly.

Kindly provide a good problem description.  Don't say "I run initdb.exe",
tell us how exactly you ran it, and what you ran before that to provoke the error.
What was your OS locale at that time? What was the exact error message?
What exactly did you have to change in the registry to make the problem go away?

Yours,
Laurenz Albe