Re: BUG #18098: Console code page issue Postgresql 14.7

From: Gokul Krishnan <gokulkrishnan99102(at)gmail(dot)com>
To: gokulkrishnan99102(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18098: Console code page issue Postgresql 14.7
Date: 2023-09-08 06:32:42
Message-ID: CAL75wykjWTEBJ9VsSe8RM=E1YjvVhQ9BJ-ogqQDQJJJBUA6qZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Team,
Since setting the chcp command on the registry is recommended by
microsoft. We cannot go with the clearing registry option. Kindly provide
the solution accordingly.

Thanks & Regards,
Gokul

On Fri, Sep 8, 2023 at 11:59 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18098
> Logged by: Gokul
> Email address: gokulkrishnan99102(at)gmail(dot)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
>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-09-08 06:36:20 BUG #18099: ERROR: could not access status of transaction 4007513275
Previous Message PG Bug reporting form 2023-09-08 06:28:13 BUG #18098: Console code page issue Postgresql 14.7