| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mendola Gaetano" <mendola(at)bigfoot(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Function immutable is not during a reindex ? |
| Date: | 2003-07-13 15:21:06 |
| Message-ID: | 22172.1058109666@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
"Mendola Gaetano" <mendola(at)bigfoot(dot)com> writes:
> On: Sunday, July 13, 2003 4:19 AM "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So? Sounds to me like it's working as intended.
> Well the documentation says:
> IMMUTABLE [...] If this option is given,
> any call of the function with all-constant
> arguments can be immediately replaced
> with the function value.
Note it says "can be", not "always will be". IMMUTABLE is a promise
you make to the system about the function's behavior ... not vice
versa.
> Used as default value:
> # alter table t_a alter b set default test(3);
> NOTICE: test called
> ALTER TABLE
> #\d t_a
> Table "public.t_a"
> Column | Type | Modifiers
> --------+---------+-----------
> a | integer |
> b | integer | default 4
This is a bug, or at least a bad idea in hindsight, and 7.4 doesn't
do it anymore.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mendola Gaetano | 2003-07-13 18:08:41 | Re: Function immutable is not during a reindex ? |
| Previous Message | Andrew Biagioni | 2003-07-13 14:16:33 | Re: Installazione Postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Szepe | 2003-07-13 16:24:28 | segfault at aset.c:539 |
| Previous Message | Mendola Gaetano | 2003-07-13 12:12:15 | Re: Function immutable is not during a reindex ? |