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

Re: pg_proc probin misuse

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PFC <lists(at)peufeu(dot)com>, James William Pye <pgsql(at)jwp(dot)name>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_proc probin misuse
Date: 2006-05-29 21:50:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Is there a TODO here?


Tom Lane wrote:
> PFC <lists(at)peufeu(dot)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

  + If your life is a hard drive, Christ can be your backup. +

In response to


pgsql-hackers by date

Next:From: PFCDate: 2006-05-29 22:10:43
Subject: Re: pg_proc probin misuse
Previous:From: Bruce MomjianDate: 2006-05-29 21:47:00
Subject: psql strings and ''

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