From: | Andriy Tkachuk <ant(at)imt(dot)com(dot)ua> |
---|---|
To: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: IMMUTABLE function's flag do not work: 7.3.4, plpgsql |
Date: | 2003-10-10 07:15:47 |
Message-ID: | 20031010101408.G35607-100000@pool.imt.com.ua |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 9 Oct 2003, Gaetano Mendola wrote:
> Andriy Tkachuk wrote:
> > On Wed, 8 Oct 2003, Tom Lane wrote:
> >
> >
> >>Andriy Tkachuk <ant(at)imt(dot)com(dot)ua> writes:
> >>
> >>>At second. calc_total() is immutable function:
> >>>but it seems that it's not cached in one session:
> >>
> >>It's not supposed to be.
> >
> >
> > but it's written id doc:
> >
> > IMMUTABLE indicates that the function always returns the same
> > result when given the same argument values; that is, it does not
> > do database lookups or otherwise use information not directly
> > present in its parameter list. If this option is given, any call
> > of the function with all-constant arguments can be immediately
> > replaced with the function value.
>
> The doc say "can be" not must and will be.
ok, but on what it depends on?
thanks,
andriy
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-10-10 07:43:09 | Re: OFFTOPIC: PostgreSQL vs MySQL |
Previous Message | Christopher Kings-Lynne | 2003-10-10 05:34:34 | Re: Speeding up Aggregates |