Yes, It worked for me also.. So will this be a workaround? Or do we intend to use something like Py_SetPythonHome() before calling Py_Initialize()/
On Wed, Aug 22, 2012 at 3:32 PM, Jan Urbański <wulc...@wulczer.org> wrote: > On 21/08/12 20:13, Josh Berkus wrote: > >> >> No. I get the same backtrace when I try against the 9.1.5 (REL9_1_STABLE) >>> branch. >>> >> > I have reproduced this on Linux, seems like the fix is to to run the > postmaster with this env variable exported: > > PYTHONHOME=/opt/ActivePython-**3.2/ > > (or wherever you installed ActivePython). > > To give credit, I found the decisive clue here: > http://manojadinesh.blogspot.**com/2012/06/fatal-python-** > error-pyinitialize-unable.html<http://manojadinesh.blogspot.com/2012/06/fatal-python-error-pyinitialize-unable.html> > > Cheers, > Jan > -- Regards, Sachin Srivastava EnterpriseDB, India
