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 EA6F9D1DFFE for ; Fri, 20 Feb 2004 15:56:43 +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 19163-09 for ; Fri, 20 Feb 2004 11:56:39 -0400 (AST) Received: from serwer.skawsoft.com.pl (skawina.eu.org [80.48.213.66]) by svr1.postgresql.org (Postfix) with ESMTP id F412DD1B456 for ; Fri, 20 Feb 2004 11:56:33 -0400 (AST) Received: from klaster.net (backbone.zab.citynet.pl [212.244.6.69]) by serwer.skawsoft.com.pl (Postfix) with ESMTP id E0DE02B3CB; Fri, 20 Feb 2004 16:56:20 +0100 (CET) Message-ID: <40362EEB.9050103@klaster.net> Date: Fri, 20 Feb 2004 16:59:39 +0100 From: Tomasz Myrta User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; pl-PL; rv:1.6) Gecko/20040113 X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: Bill Moran Cc: pgsql-performance@postgresql.org Subject: Re: cacheable stored functions? References: <40362944.2060809@potentialtech.com> In-Reply-To: <40362944.2060809@potentialtech.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/238 X-Sequence-Number: 5762 Dnia 2004-02-20 16:35, Użytkownik Bill Moran napisał: > Can anyone say whether this is a supported feature in plpgsql, and is > safe to use? Is it simply undocumented, or am I just looking in the > wrong place? "iscachable" is only for backward compatibility - it's changed now to "IMMUTABLE" You can read more about immutable, stable and volatile functions in Postgresql documentation - chapter SQL Commands/CREATE FUNCTION. Regards, Tomasz Myrta