Re: Using scalar function as set-returning: bug or feature?

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Tels <nospam-pg-abuse(at)bloodgate(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Using scalar function as set-returning: bug or feature?
Date: 2018-02-13 11:35:08
Message-ID: CAL9smLALdNruR_3_Oqw+DENyadbzVt0i3fVKpxNO=BoZjadJYA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 13, 2018 at 12:30 PM, Tels <nospam-pg-abuse(at)bloodgate(dot)com>
wrote:

> I'm not sure if you mean exactly the scenario as in the attached test
> case, but this works in plpgsql, too, and would be a shame to lose.
>
> OTOH, one could also write:
>
> SELECT INTO ba, bb a,b FROM foo(1);
>
> and it would still work, or wouldn't it?
>

Yes. The code in test.psql shouldn't pass code review.

.m

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2018-02-13 12:40:46 Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
Previous Message Tels 2018-02-13 11:30:53 Re: Using scalar function as set-returning: bug or feature?