On tis, 2010-07-06 at 18:15 -0400, Tom Lane wrote:
At this point it seems clear to me that we've not adequately thought
through the implications of having two python versions in one
application namespace, and I'm not sure the Python people have either.
I think we need to do something to block
Peter Eisentraut pete...@gmx.net writes:
On tis, 2010-07-06 at 18:15 -0400, Tom Lane wrote:
At this point it seems clear to me that we've not adequately thought
through the implications of having two python versions in one
application namespace, and I'm not sure the Python people have either.
pet...@postgresql.org (Peter Eisentraut) writes:
Log Message:
---
Add note that using PL/Python 2 and 3 in the same session will probably crash
Crash? I can see people regarding that as a security problem. Maybe we
need to do something more pro-active to prevent such conflicts?
On tis, 2010-07-06 at 17:49 -0400, Tom Lane wrote:
pet...@postgresql.org (Peter Eisentraut) writes:
Log Message:
---
Add note that using PL/Python 2 and 3 in the same session will probably
crash
Crash? I can see people regarding that as a security problem. Maybe we
need to
On Tue, 2010-07-06 at 17:49 -0400, Tom Lane wrote:
pet...@postgresql.org (Peter Eisentraut) writes:
Log Message:
---
Add note that using PL/Python 2 and 3 in the same session will probably
crash
Crash? I can see people regarding that as a security problem. Maybe we
need to
Peter Eisentraut pete...@gmx.net writes:
On tis, 2010-07-06 at 17:49 -0400, Tom Lane wrote:
Crash? I can see people regarding that as a security problem. Maybe we
need to do something more pro-active to prevent such conflicts?
I don't see how. Loading any module that uses the same symbols
