Hi,
I realize it’s not a PostgreSQL database engine bug, but more of an EDB Installer bug.
I did contact Enterprise DB (EDB) and they suggested to log it in the pgsql-bugs mailing list, as I am using the “community” version of the Windows installer (i.e. no paid support).
Hopefully, someone from EDB will look at it and eventually address it.
In the end, the problem should be addressed by BeyondTrust as it is their software that is causing the problems. The issue has been that the vendor has been unable to resolve the issue to date. This is why I have been trying this “alternative” route instead.
Thanks,
Joel
From: David G. Johnston <david.g.johnston@gmail.com>
Sent: Tuesday, May 23, 2023 5:47 PM
To: Joel Rabinovitch <Joel.Rabinovitch@tecsys.com>; pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17940: PostgreSQL Installer For Windows Cannot Initialize Cluster When BeyondTrust Installed
ATTENTION: This email originated from outside of Tecsys. Use caution when clicking links or opening attachments. | Ce courriel provient de l'extérieur de Tecsys. Soyez prudent lorsque vous cliquez sur des liens ou ouvrez des pièces jointes.
The following bug has been logged on the website:
Bug reference: 17940
Logged by: Joel Rabinovitch
Email address: joel.rabinovitch@tecsys.com
PostgreSQL version: 13.4
Operating system: Microsoft Windows 10
Description:
Our developers do their work using a local PostgreSQL database server and
local schemas.
This is typically done by installing the Windows version of the PostgreSQL
installer from EnterpriseDB. Currently, version 13.4 (64-bit) of the
installer is being used.
This isn't a PostgreSQL bug. Your original posting of this to the -general list is the most appropriate place on the official lists to ask for such help. That said, the core community on these lists does not maintain the EDB installer and you may wish to use their support channels to get further assistance.
That all said, I'm not expecting the PostgreSQL side of this to be of much help. The software installation and usage works just fine in typical environments. As your special security restricted environment is the outlier you probably will either need to simply move along with your workaround or hope that vendor can figure out how to let the installer work in the manner it is designed to work.
