Re: pg_proc probin misuse - Mailing list pgsql-hackers

From PFC
Subject Re: pg_proc probin misuse
Date
Msg-id op.taara1a3cigqcu@apollo13
Whole thread Raw
In response to Re: pg_proc probin misuse  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_proc probin misuse
List pgsql-hackers
> 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).


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: non-transactional pg_class
Next
From: Hannu Krosing
Date:
Subject: Re: COPY FROM view