Re: pg_proc probin misuse
| От | Tom Lane |
|---|---|
| Тема | Re: pg_proc probin misuse |
| Дата | |
| Msg-id | 13001.1148910842@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: pg_proc probin misuse (PFC <lists@peufeu.com>) |
| Ответы |
Re: pg_proc probin misuse
|
| Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: