On tis, 2010-07-13 at 20:28 -0500, Chris wrote: > So if I have to explicitly set the python interpretor, how would you > ever have a plpython2u and plpython3u function in the same DB > (regardless of the fact that they can't run in the same session)? The > manual implies you could have them both installed since it says that > there's a per session limitation. After specifying the python3 > interpretor, I can indeed now run plpython3u, but I (rather obviously) > can't createlang plpython2u now. > I would think that the plpython section of the manual may want some > reference to that fact that that compile flag needs to be set.
Added documentation about that. > Additionally, "What's New In Python 3.0 " for the beta 3 docs on > http://www.postgresql.org/docs/9.0/static/plpython-python23.html is > dead. And fixed that. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
