| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Joseph S <jks(at)selectacast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Static functions |
| Date: | 2008-10-05 12:46:41 |
| Message-ID: | 20081005124641.GA1954@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Oct 04, 2008 at 08:30:32PM -0400, Joseph S wrote:
> In this case, with the function being called over and over again inside
> a nested loop, it would be worth the effort. I'm not even talking about
> caching the result for the whole transaction block, just replacing the
> function call before continuing the query.
I think you're going to have to be more specific, because if the
function is stable or immutable, pg will do exactly as you say. Post
the actual query involved.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-10-05 15:02:44 | Re: db_user_namespace, md5 and changing passwords |
| Previous Message | Joshua D. Drake | 2008-10-05 05:50:42 | Re: db_user_namespace, md5 and changing passwords |