> If it were really expensive to derive bytecode from source text
> then maybe it'd make sense to do what you're doing, but surely that's
> not all that expensive. Everyone else manages to parse prosrc on the
> fly and cache the result in memory; why isn't plpython doing that?
It depends on the number of imported modules in the function. If it
imports a lot of modules, it can take some time to compile a python
function (especially if the modules have some initialisation code which
must be run on import).
In response to
pgsql-hackers by date
|Next:||From: Thomas Hallgren||Date: 2006-05-29 06:01:07|
|Subject: Re: Inefficient bytea escaping?|
|Previous:||From: Alvaro Herrera||Date: 2006-05-29 04:53:02|
|Subject: non-transactional pg_class|