From: "Pavel Kulakov" <paul.kulakov@systematica.ru>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>
Cc: <pgsql-bugs@lists.postgresql.org>
References: <18195-95ee8b48a9d7cd93@postgresql.org>
 <2486681.1699975861@sss.pgh.pa.us>
In-Reply-To: <2486681.1699975861@sss.pgh.pa.us>
Subject: RE: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO
 statement
Date: Wed, 15 Nov 2023 10:22:53 +0300
Message-ID: <001501da1794$8c3baa10$a4b2fe30$@systematica.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Language: ru
Thread-Index: AQHU2ZXcvcQNKHg1XihmYBUfGbDXmQI/xV33sHN1/MA=
Archived-At: 
 <https://www.postgresql.org/message-id/001501da1794%248c3baa10%24a4b2fe30%24%40systematica.ru>
Precedence: bulk

Hi Tom,

Thanks for your answer.
I set plpgsql.extra_errors = 'strict_multi_assignment'

Now, how to explain the following working?

do $sql$
declare
   _n int; _s text;
begin
   select 1 into _n _s;
   raise notice '_n = %, _s = %', _n, _s;
end;
$sql$;

Regards,
Pavel

-----Original Message-----
From: Tom Lane <tgl@sss.pgh.pa.us> 
Sent: Tuesday, November 14, 2023 6:31 PM
To: paul.kulakov@systematica.ru
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO
statement

PG Bug reporting form <noreply@postgresql.org> writes:
> 1. The following code is successfully executed although it has 
> incorrect
> syntax: there must be comma (,) between _n and _s in 'into' section.

>    select 1, 'string1', 'string2'
>    into _n _s;

I believe this is being read the same as

    select 1, 'string1', 'string2' _s into _n;

That is, the lack of a comma causes the INTO sub-clause to end, and then _s
is taken as an AS-less column label.  As the manual explains, for
backwards-compatibility reasons we allow INTO to be embedded anywhere in the
command, even though that leads to surprising-looking cases like this one.

As for the question of why you don't get an error for the wrong number of
INTO targets, again that's backwards compatibility.
There's a "strict_multi_assignment" check you can turn on to make it
complain about that [1].

			regards, tom lane

[1]
https://www.postgresql.org/docs/current/plpgsql-development-tips.html#PLPGSQ
L-EXTRA-CHECKS