Re: pg_proc probin misuse - Mailing list pgsql-hackers

From PFC
Subject Re: pg_proc probin misuse
Date
Msg-id op.tab2j5ekcigqcu@apollo13
Whole thread Raw
In response to Re: pg_proc probin misuse  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Hm, thinking again, I guess Tom Lane is right

>> 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?
Besides, what happens if you store compiled bytecode in a table, then  
upgrade the python interpreter to a new version... would it be compatible  
? I suppose so, but I don't really know...Persistent connections should be used anyway, this makes the RAM caching  
good...


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_proc probin misuse
Next
From: Bruce Momjian
Date:
Subject: Re: Inefficient bytea escaping?