| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Neil Conway" <neilc(at)samurai(dot)com> |
| Cc: | "Brendan Jurd" <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: FOUND with EXECUTE |
| Date: | 2007-10-16 05:08:20 |
| Message-ID: | 162867790710152208k701720c3xa1d6103318883486@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2007/10/16, Neil Conway <neilc(at)samurai(dot)com>:
> On Tue, 2007-10-16 at 11:24 +1000, Brendan Jurd wrote:
> > Is there a technical reason we do not set the value of FOUND when
> > executing a dynamic statement in plpgsql?
>
> See prior discussion:
>
> http://archives.postgresql.org/pgsql-bugs/2004-10/msg00001.php
>
> It would be easy enough to have EXECUTE modify FOUND, and that might
> well be worth doing. Adding an "EVAL" concept would also be useful,
> though, and would avoid changing EXECUTE's behavior in a way that might
> break client apps.
>
> -Neil
>
>
It's symply. But other execute statement only will more uglyze plpgsql.
use GET DIAGNOSTICS statement a wait for sql/psm
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2007-10-16 05:11:20 | Re: V3 protocol is slower than V2 |
| Previous Message | Brendan Jurd | 2007-10-16 05:06:59 | Re: plpgsql: Plan type mismatch error |