Re: Function is called multiple times in subselect

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Alex J(dot) Avriette" <alex(at)posixnap(dot)net>
Cc: Chris Campbell <chris(at)bignerdranch(dot)com>, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>, Don Marco <mark(at)bignerdranch(dot)com>, Aaron Hillegass <aaron(at)bignerdranch(dot)com>
Subject: Re: Function is called multiple times in subselect
Date: 2004-03-12 14:41:39
Message-ID: 8978.1079102499@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Alex J. Avriette" <alex(at)posixnap(dot)net> writes:
> And if you are concerned about the query's cost vs its actual output
> (you weren't clear in your original message), there is the 'iscachable'
> pragma for functions.

I think that's unrelated to Chris' problem.

One of the reasons we renamed that pragma to "immutable" is that too
many people were interpreting it as suggesting that Postgres would do
some kind of caching of the function's results. There is no such cache.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris Campbell 2004-03-12 16:01:37 Re: Function is called multiple times in subselect
Previous Message Alex J. Avriette 2004-03-12 10:55:49 Re: Function is called multiple times in subselect