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

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Marko Tiikkaja <marko(at)joh(dot)to>
Cc: 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-09 11:10:11
Message-ID: CAFj8pRCY7WXO7BSMCP6+VAjoHaiUkAxHxcjSfjVFybqOZxcFKA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2018-02-09 12:02 GMT+01:00 Marko Tiikkaja <marko(at)joh(dot)to>:

> On Fri, Feb 9, 2018 at 9:58 AM, Konstantin Knizhnik <
> k(dot)knizhnik(at)postgrespro(dot)ru> wrote:
>
>> Attached please find patch reporting error in case of empty attribute
>> list for SELECT INTO
>>
>
> This is quite short-sighted. The better way to do this is to complain if
> the number of expressions is different from the number of target variables
> (and the target variable is not a record-ish type). There's been at least
> two patches for this earlier (one my me, and one by, I think Pavel
> Stehule). I urge you to dig around in the archives to avoid wasting your
> time.
>

This issue can be detected by plpgsql_check and commitfest pipe is patch
that raise warning or error in this case.

Regards

Pavel

>
>
> .m
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ildar Musin 2018-02-09 11:49:29 Re: Proposal: partition pruning by secondary attributes
Previous Message Pavel Stehule 2018-02-09 11:02:57 Re: CALL stmt, ERROR: unrecognized node type: 113 bug