| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Valentine Gogichashvili <valgog(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: Can't use WITH in a PERFORM query in PL/pgSQL? |
| Date: | 2011-10-20 17:33:37 |
| Message-ID: | CAFj8pRC1be1ckLOhiJpSQBpWs1ijLh=poRrCpFRbrsEtmKTNqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2011/10/20 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Valentine Gogichashvili <valgog(at)gmail(dot)com> writes:
>> And, ernestly, if it were useless to have SELECT without INTO in plpgsql,
>> there also would be no PERFORM command in plpgsql...
>
> Precisely. Pavel's claim is nonsense. The only real question is how
> useful is it to call it PERFORM instead of SELECT.
I didn't design a PERFORM statement. There is two views - somebody
from sybase's family know so SELECT without into is forwarded to
client. This functionality is missing on Oracle's family. Is true so
PERFORM statement is strange, but maybe it's open door for sybase's
functionality that was not implemented ever.
Regards
Pavel Stehule
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-10-20 17:35:36 | Re: BUG #6263: \l causes core dump with large database |
| Previous Message | Tom Lane | 2011-10-20 17:15:33 | Re: Can't use WITH in a PERFORM query in PL/pgSQL? |