From: | Terje Elde <terje(at)elde(dot)net> |
---|---|
To: | george(dot)wesington(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13823: Database crash - import requests in plpython3u |
Date: | 2015-12-18 05:59:28 |
Message-ID: | 01D7F600-660B-44AE-86CC-F56BD563DD2F@elde.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> On 17 Dec 2015, at 14:34, george(dot)wesington(at)gmail(dot)com wrote:
>
> After the crash the database needs to be restarted because it cannot be
> accessed anymore. The same script runs perfectly when run directly from
> python.
>
> Let me know if you need any more information.
Could you try to run it as the PostgreSQL user, but outside PostgreSQL?
Also, please double check that it's run as Python 3 when testing that. The code looks fairly compatible between 2.7 and 3.x, and my best initial guess would be that Python crashes on a missing or faulty import.
Can you successfully run a simpler Python function from PostgreSQL? (One that doesn't import anything). Easy way to narrow down if it's likely the requests-module in Python, or if it's related to plpython.
Oh, and how did you install Python, PostgreSQL, plpython and the requests module?
Terje
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2015-12-18 07:09:40 | Re: BUG #13817: Query planner strange choose while select/count small part of big table - complete |
Previous Message | Michael Paquier | 2015-12-18 05:04:41 | Re: BUG #13822: Slave terminated - WAL contains references to invalid page |