| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | "Bob Henkel" <bob(at)teamhenkel(dot)com> | 
| Cc: | pgsql-bugs(at)postgresql(dot)org | 
| Subject: | Re: BUG #1215: Call sql function from plpgsql results vary. | 
| Date: | 2004-08-12 03:06:09 | 
| Message-ID: | 23560.1092279969@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-bugs | 
"PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> I was playing around seeing what new things I could do in stored procedures.
> Here is the statment I'm using to get the issue.
> select * from f_trap_error();
> I expect the above statement to alway return 1 which it does.
> The issue is I expect the trapped_error table to contain a seq id and than a 
> 999 899 
I think the problem is you declared f_test_sql as IMMUTABLE, which
entitles the planner to execute it once and bind the result as a
constant.  Functions with side-effects should *never* be marked
immutable (nor stable for that matter).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Henkel | 2004-08-12 03:41:28 | Re: BUG #1215: Call sql function from plpgsql results vary. | 
| Previous Message | Michael Fuhr | 2004-08-12 02:56:27 | 8.0.0beta1: Ownership of implicit sequences after dump/restore |