[COMMITTERS] pgsql: Add note that using PL/Python 2and 3 in the same session will
in [PgSql]
|
Prev: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will
Next: Does mbutils.c really need to use L'\0' ?
From: Peter Eisentraut on 6 Jul 2010 17:54 On tis, 2010-07-06 at 17:49 -0400, Tom Lane wrote: > petere(a)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? I don't see how. Loading any module that uses the same symbols as another already loaded modules can cause the same problem. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Joshua D. Drake" on 6 Jul 2010 17:54 On Tue, 2010-07-06 at 17:49 -0400, Tom Lane wrote: > petere(a)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? +1 Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Peter Eisentraut on 7 Jul 2010 17:05 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 that from happening, at least > until we have a plausible way to make it work. How about this?
From: Peter Eisentraut on 8 Jul 2010 14:40
On ons, 2010-07-07 at 17:31 -0400, Tom Lane wrote: > Yeah, I was going to suggest something involving > find_rendezvous_variable to let the two versions of plpython check for > each other. But doesn't the error need to be elog(FATAL)? If you > just > elog(ERROR) then the conflicting version of python.so is already > loaded > and able to cause problems. elog(FATAL) isn't very desirable maybe > but it beats crashing. Done -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |