| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: cacheable stored functions? |
| Date: | 2004-02-20 15:47:33 |
| Message-ID: | 20040220074336.G82937@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 20 Feb 2004, 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.
It's been basically superceded by IMMUTABLE, and I believe they're
described in the create function reference page. Note that it doesn't
involve caching as much as the fact that it can be evaluated once and
treated as a constant.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Myrta | 2004-02-20 15:59:39 | Re: cacheable stored functions? |
| Previous Message | Bill Moran | 2004-02-20 15:35:32 | cacheable stored functions? |