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

Re: pg_proc probin misuse

From: PFC <lists(at)peufeu(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "James William Pye" <pgsql(at)jwp(dot)name>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_proc probin misuse
Date: 2006-05-29 05:10:03
Message-ID: op.taara1a3cigqcu@apollo13 (view raw or flat)
Thread:
Lists: 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).

In response to

Responses

pgsql-hackers by date

Next:From: Thomas HallgrenDate: 2006-05-29 06:01:07
Subject: Re: Inefficient bytea escaping?
Previous:From: Alvaro HerreraDate: 2006-05-29 04:53:02
Subject: non-transactional pg_class

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