| From: | Sachin Srivastava <sachin(dot)srivastava(at)enterprisedb(dot)com> |
|---|---|
| To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL 9.2beta4 (& git HEAD) server crash on creating extension plpython3u |
| Date: | 2012-08-22 11:28:02 |
| Message-ID: | CA+RD+khu89VZLc+JhfUiZBz5_=z_=Qfj3O1YwzwbpJ4bW_e+0w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 <wulczer(at)wulczer(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-08-22 12:02:21 | Re: 64-bit API for large object |
| Previous Message | Jan Urbański | 2012-08-22 10:02:59 | Re: PostgreSQL 9.2beta4 (& git HEAD) server crash on creating extension plpython3u |