Re: pg_proc probin misuse

Is there a TODO here?

---------------------------------------------------------------------------

Tom Lane wrote:
> PFC <lists@peufeu.com> writes:
> >> 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).
> 
> Surely the initialization code would have to be run anyway ... and if
> the function does import a pile of modules, do you really want to cache
> all that in its pg_proc entry?  What happens if some of the modules get
> updated later?
> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
> 

--  Bruce Momjian   http://candle.pha.pa.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +