Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 738C61337B67 for ; Mon, 29 Nov 2010 09:30:06 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 79401-07-3 for ; Mon, 29 Nov 2010 13:29:59 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com [209.85.213.46]) by mail.postgresql.org (Postfix) with ESMTP id 002D51337BC7 for ; Mon, 29 Nov 2010 09:29:58 -0400 (AST) Received: by ywl5 with SMTP id 5so1983557ywl.19 for ; Mon, 29 Nov 2010 05:29:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:cc :subject:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=o87FCN5IEBLauoOLn8D8voqFDNFjKUDStiq3ffcWELc=; b=jsEQV9TXhUVdOJ7vZ9roFRNqB42sPcmGSob22GW3GzZT4djGHYZcW31m2EUmaXjcW+ qKbaCw7Tc7N4zTigGDP6gTukf9T+8V8sTDLUW/6/VXcJhpBow2YacZe6tLRqG9BFykvt rd2gLGgS0a4meGmv9IdLCuD3u1nAiJTW5JtmY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:cc:subject:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=EULJD6+Ph3v5VHr+sthAFoQzFensce/PdsPv48cQUzSaHRrlSXiTmvNKeefPXxwU1M kOymGi7Gl1lv21yEzPFHbg8K8hiqd1oqScYRv/nHB6S+QJ3F7Kp6tgjHkotTsOvWaZU+ /lXdQHDd4aOwlVVPO2Xm4y1PZR7fXSoAMjTdY= Received: by 10.90.38.27 with SMTP id l27mr2171779agl.116.1291037399142; Mon, 29 Nov 2010 05:29:59 -0800 (PST) Received: from eddie (c-67-186-249-122.hsd1.ut.comcast.net [67.186.249.122]) by mx.google.com with ESMTPS id e24sm5769363ana.22.2010.11.29.05.29.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 29 Nov 2010 05:29:57 -0800 (PST) Message-ID: <4cf3aad5.1838640a.6f25.232e@mx.google.com> Date: Mon, 29 Nov 2010 06:29:31 -0700 From: Joshua Tolley To: c k Cc: Martin Gainty , "pgsql-general@postgresql.org" Subject: Re: plpyhton References: <4cedf777.2a978e0a.619c.164d@mx.google.com> <4cefdab2.16958e0a.588d.ffff9748@mx.google.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PdAWLd+WEPmMbsbx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201011/1166 X-Sequence-Number: 170232 --PdAWLd+WEPmMbsbx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 27, 2010 at 04:38:27PM +0530, c k wrote: > How can we implement procedure cache? Cane you please give details regard= ing > this? > It will be helpful for me. This is something the PL implementation needs to do for you. I finally look= ed at the plpython code, and found that it does indeed do this for you. PLPyth= on caches a procedure's input and return types, and a compiled representation = of the procedure's source.=20 -- Joshua Tolley / eggyknap End Point Corporation http://www.endpoint.com --PdAWLd+WEPmMbsbx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkzzqrsACgkQRiRfCGf1UMM5MQCfXOdVwYL/BEnQxx6jjK3fJZos Q2IAn0nc4fzPLJrgBmrOKslM0rC1TVMw =GKOv -----END PGP SIGNATURE----- --PdAWLd+WEPmMbsbx--