| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)justatheory(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>, 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:48:26 |
| Message-ID: | 20130829214826.GA4283@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-08-29 14:40:24 -0700, Josh Berkus wrote:
> On 08/29/2013 02:22 PM, Pavel Stehule 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.
>
> You have yet to supply any arguments which support this position.
I am not convinced that's enough of a reason, but the requirement to use
PERFORM for SELECTs that aren't stored anywhere actually has prevented
bugs for me. I am not convinced that's worth the cost since I also have
been annoyed by it several times, but it's not as crystal clear as you
paint it.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-08-29 21:50:16 | Re: PL/pgSQL PERFORM with CTE |
| Previous Message | David E. Wheeler | 2013-08-29 21:45:21 | Re: PL/pgSQL PERFORM with CTE |