| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Chris <rfusca(at)gmail(dot)com> |
| Subject: | Re: testing plpython3u on 9.0beta2 |
| Date: | 2010-06-29 00:19:28 |
| Message-ID: | 1277770768.27966.6.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On fre, 2010-06-25 at 18:57 -0400, Peter Eisentraut wrote:
> On fre, 2010-06-25 at 23:44 +0200, Andres Freund wrote:
> > Has anybody actually researched if it is safe to run python2 and
> > python3 in the same address space?
>
> You can't run plpython2 and plpython3 in the same session, because the
> libraries are loaded with dlopen(RTLD_GLOBAL) (with RTLD_LOCAL it would
> apparently work). But you can use them in different sessions on the
> same database, for example.
By the way, I thought there had been some discussion about this in the
past, but I couldn't find it ...
Why are we using RTLD_GLOBAL?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-06-29 00:24:09 | Re: Keepalives win32 |
| Previous Message | Mark Kirkwood | 2010-06-28 23:52:58 | Re: Admission Control |