From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: cacheable stored functions? |
Date: | 2004-02-20 16:01:28 |
Message-ID: | 200402201601.28789.dev@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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.
From memory, "iscachable" was replaced in version 7.3 by the three
finer-grained settings IMMUTABLE, STABLE, VOLATILE.
I'm guessing the old behaviour is still there for backwards compatibility, but
it's probably best to use the new versions.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2004-02-20 16:48:24 | Re: cacheable stored functions? |
Previous Message | Tomasz Myrta | 2004-02-20 15:59:39 | Re: cacheable stored functions? |