From: | Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com> |
---|---|
To: | gursharan(dot)panesar(at)bnpparibas(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18707: Installation issue |
Date: | 2024-12-03 06:03:20 |
Message-ID: | CANFyU95JMQ3U1=N_NvY4K4vZ4=3r5F91cRa-YLWvo4bQtcKnnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi Gurusharan,
PostgreSQL 17.2-2, 16.6-2, 15.10-2 are available for download. These
installers include a fix when the local system is a non-English name
containing non-ASCII characters. Please have a look. Hopefully, it should
resolve the issue for you.
Thank you for your patience.
On Thu, Nov 14, 2024 at 7:51 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18707
> Logged by: Gursh Panesar
> Email address: gursharan(dot)panesar(at)bnpparibas(dot)com
> PostgreSQL version: 15.8
> Operating system: Windows 10
> Description:
>
> We have an issue installing version 15.8 using file
> postgresql-15.8-1-windows-x64.exe.
> The installation in our environment is run in the system context.
> When the installation is run in the system context it writes to
> C:\Windows\Temp folder and fails.
> If the installation is run as admin, it writes to %LocalAppData%\Temp.
> The previous version of the installer was able to run in system context and
> install the application without any issue.
>
> Each time the installation is run in system context, it generates a folder
> with a different name so we cannot change the permission. If the temp
> folder
> can have a fixed name, then it may be possible to change the permissions.
>
>
--
Sandeep Thakkar
From | Date | Subject | |
---|---|---|---|
Next Message | Bertrand Drouvot | 2024-12-03 07:38:56 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |
Previous Message | Tom Lane | 2024-12-03 01:41:01 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |