From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
---|---|
To: | c k <shreeseva(dot)learning(at)gmail(dot)com> |
Cc: | Martin Gainty <mgainty(at)hotmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: plpyhton |
Date: | 2010-11-29 13:29:31 |
Message-ID: | 4cf3aad5.1838640a.6f25.232e@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Sat, Nov 27, 2010 at 04:38:27PM +0530, c k wrote:
> How can we implement procedure cache? Cane you please give details regarding
> this?
> It will be helpful for me.
This is something the PL implementation needs to do for you. I finally looked
at the plpython code, and found that it does indeed do this for you. PLPython
caches a procedure's input and return types, and a compiled representation of
the procedure's source.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
From | Date | Subject | |
---|---|---|---|
Next Message | Silvio Brandani | 2010-11-29 14:13:01 | data mount point lost permissions |
Previous Message | Seifert, Jan-Peter | 2010-11-29 10:36:28 | Re: trouble creating a tablespace on win2k8r2 with pg9.0 |
From | Date | Subject | |
---|---|---|---|
Next Message | Reto Schöning | 2010-11-29 14:27:35 | Re: "could not accept SSPI security context" |
Previous Message | Vick Khera | 2010-11-29 13:17:16 | Re: ERROR: xlog flush request 17/4D6C2720 is not satisfied |