Re: PlPython - Mailing list pgsql-general

From elein
Subject Re: PlPython
Date
Msg-id 200306301444.23047.elein@varlena.com
Whole thread Raw
In response to Re: PlPython  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PlPython  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
The global data (GD) and function data (SD)
work as they always have worked.  That is the
part I was most anxious to test.

GD is sharable between any python functions.
It always was.  It is a memory leak hazard with warnings.

SD is sharable within the same *connection*
only by the same function (name+argtypes).
The scope of SD is kinda weird but is
consistent with its previous behaviour.

(I did rerun those tests on the newly correctly
built versions.)

elein

On Monday 30 June 2003 14:32, Tom Lane wrote:
> elein  <elein@varlena.com> writes:
> > Sorry about the mixup earlier.  But the "forbidden"
> > modules part still needs to be tossed for the new doc.
>
> Right.  I already pulled section 43.4 --- see the updated docs at
> http://developer.postgresql.org/docs/postgres/plpython.html
>
> I've also commented out the paragraph about global data and function
> arguments pending resolution of the question.  Given the reference to
> restricted execution objects in the original text, I would think that
> the removal of rexec usage means that plpython functions can now get at
> any global data.  But I'm not a Python user and might be
> misunderstanding the point.
>
>             regards, tom lane
>
>

--
=============================================================
elein@varlena.com     Database Consulting     www.varlena.com
PostgreSQL General Bits    http:/www.varlena.com/GeneralBits/
   "Free your mind the rest will follow" -- en vogue


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PlPython
Next
From: Tom Lane
Date:
Subject: Re: PlPython