From: | Marko Tiikkaja <marko(at)joh(dot)to> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL PERFORM with CTE |
Date: | 2013-08-20 12:59:27 |
Message-ID: | 5213682F.3040609@joh.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/20/13 2:53 PM, Pavel Stehule wrote:
> 2013/8/20 David E. Wheeler <david(at)justatheory(dot)com>
>> I am passing the values returned from a CTE to a call to pg_notify(). I do
>> not care to collect the output of pg_notify(), which returns VOID.
>>
>
> it is little bit different issue - PL/pgSQL doesn't check if returned type
> is VOID - it can be allowed, I am thinking. So check of empty result can be
> enhanced.
That still doesn't help at all in the case where the function returns
something, but you simply don't care about the result.
That said, I don't think this issue is big enough to start radically
changing how SELECT without INTO works -- you can always get around this
limitation by SELECTing into a variable, as David mentioned in his
original message. It's annoying, but it works.
Regards,
Marko Tiikkaja
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2013-08-20 13:01:10 | Re: PL/pgSQL PERFORM with CTE |
Previous Message | Pavel Stehule | 2013-08-20 12:53:22 | Re: PL/pgSQL PERFORM with CTE |