Skip site navigation (1) Skip section navigation (2)

Re: PlPython

From: elein <elein(at)varlena(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>,joconnor(at)cybermesa(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: PlPython
Date: 2003-06-30 21:44:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
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.)


On Monday 30 June 2003 14:32, Tom Lane wrote:
> elein  <elein(at)varlena(dot)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
> 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(at)varlena(dot)com     Database Consulting
PostgreSQL General Bits    http:/
   "Free your mind the rest will follow" -- en vogue

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2003-06-30 21:49:40
Subject: Re: PlPython
Previous:From: Tom LaneDate: 2003-06-30 21:38:21
Subject: Re: Is Patch Ok for deferred trigger disk queue?

pgsql-general by date

Next:From: Tom LaneDate: 2003-06-30 21:49:40
Subject: Re: PlPython
Previous:From: Kevin JacobsDate: 2003-06-30 21:36:36
Subject: Re: PlPython

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group