| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Chris <rfusca(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: testing plpython3u on 9.0beta3 |
| Date: | 2010-09-08 20:36:53 |
| Message-ID: | 1283978213.3652.0.camel@vanquo.pezone.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-09-08 20:49:29 | Re: Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!) |
| Previous Message | Tom Lane | 2010-09-08 20:26:01 | Re: git: uh-oh |