X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 52A6BD1D570 for ; Fri, 20 Feb 2004 16:01:40 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 28695-05 for ; Fri, 20 Feb 2004 12:01:34 -0400 (AST) Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by svr1.postgresql.org (Postfix) with ESMTP id 18787D1D4E7 for ; Fri, 20 Feb 2004 12:01:34 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-31.mail.demon.net with esmtp (Exim 3.35 #1) id 1AuD5o-0008K3-0V; Fri, 20 Feb 2004 16:01:32 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id 33A0A163B3; Fri, 20 Feb 2004 16:01:31 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 3004615951; Fri, 20 Feb 2004 16:01:29 +0000 (GMT) From: Richard Huxton To: Bill Moran , pgsql-performance@postgresql.org Subject: Re: cacheable stored functions? Date: Fri, 20 Feb 2004 16:01:28 +0000 User-Agent: KMail/1.5 References: <40362944.2060809@potentialtech.com> In-Reply-To: <40362944.2060809@potentialtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402201601.28789.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/239 X-Sequence-Number: 5763 On Friday 20 February 2004 15:35, Bill Moran wrote: > I'm converting a SQL application to PostgreSQL. The majority of the logic > in this application is in the stored functions in the database. > > Somewhere, I saw a reference to "WITH (iscachable)" for stored functions, > looking again, I'm unable to find any reference to this directive. I have > a single function that is _obviously_ safe to cache using this, and it > generates no errors or problems that I can see. > > Now I'm looking at a lot of other functions that, if cached, would speed > up performance considerably. Yet I'm reluctant to use this directive > since I can't find documentation on it anywhere.