| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Jan Wieck <JanWieck(at)yahoo(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL PERFORM with CTE |
| Date: | 2013-08-29 21:41:01 |
| Message-ID: | CAFj8pRCLEgYLSmzWdwgBi-QZTxiVU3PMAgYyRcZ6mQ7u9rEemg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2013/8/29 David E. Wheeler <david(at)justatheory(dot)com>
> On Aug 29, 2013, at 2:22 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
> > Still I don't think so correct solution is enabling a unbound SELECTs,
> but correct is a fix a PERFORM and remove a necessity to use a PERFORM for
> call of VOID functions.
>
> Well, in this thread, I believe you are the only person who feels that
> way. And this proposal still would not let PERFORM work with CTEs.
>
I am thinking, so I propose a enough solution for you - when you use CTE
for execution of VOID function, then result vill be VOID set, what we can
accept as undefined result, and in this case a PERFORM should not be
required. If CTE will return some result, then PERFORM should be required
and PERFORM must to support CTE in all possible modes - updateable or not
updateable queries.
Regards
Pavel
>
> Best,
>
> David
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2013-08-29 21:44:47 | Re: PL/pgSQL PERFORM with CTE |
| Previous Message | Josh Berkus | 2013-08-29 21:40:24 | Re: PL/pgSQL PERFORM with CTE |