| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL PERFORM with CTE |
| Date: | 2013-08-29 21:36:28 |
| Message-ID: | 20130829213628.GD5277@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-08-29 14:31:55 -0700, David E. Wheeler wrote:
> 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 haven't made up my mind on whether PERFORM is a good idea or not, but
independently from that we certainly could patch plpgsql to allow
PERFORM WITH .... Doesn't look to hard to me from a quick look.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-08-29 21:37:31 | Re: Variadic aggregates vs. project policy |
| Previous Message | Andres Freund | 2013-08-29 21:33:41 | Re: Master-slave visibility order |