On 05/09/2018 10:38 AM, Bruce Harold wrote:
It seems my cheap hack doesn't work, the server connection breaks on CREATE FUNCTION unless PYTHONHOME is set for the system.
Yeah, pretty sure the server is not looking at the environment that pgAdmin4 is running in as that is not part of the core.
Not sure how to solve this. I don't run Windows enough anymore to offer any suggestions. Maybe someone from EDB will chime in.
-----Original Message----- From: Bruce Harold Sent: Wednesday, May 9, 2018 9:46 AM To: 'Adrian Klaver' <adrian.klaver@xxxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxxxxxxxx Subject: RE: Error creating plpython3u extension Thank you Adrian and Jeff. I made some progress and can extend databases with plpython3u. Re. the edb doc, "C:\edb\LanguagePack-10\x64\Python-3.4\bin" does not exist, stripping 'bin' off the path is required. Setting PYTHONHOME for the system is unfriendly to the rest of my python dependencies, so to make this specific to pg I edited the pgAdmin 4 shortcut to set the variable there, the shortcut target becomes: C:\Windows\System32\cmd.exe /c "SET PYTHONHOME=C:\edb\languagepack-10\x64\Python-3.4 && START pgAdmin4.exe" The "Start in" property does not change, the executable is found. Whether or not this works across the server I guess I'll find out shortly, I'm a newbie doing a proof of concept so deployment isn't a concern. Bruce
-- Adrian Klaver adrian.klaver@xxxxxxxxxxx
