From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: kyzevan23@mail.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17561: Server crashes on executing row() with very long
 argument list
In-reply-to: <20220729101411.7b45rvhlrsgcajjo@alvherre.pgsql>
References: <20220729101411.7b45rvhlrsgcajjo@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Fri, 29 Jul 2022 12:14:11 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3753049.1659102953.1@sss.pgh.pa.us>
Date: Fri, 29 Jul 2022 09:55:53 -0400
Message-ID: <3753050.1659102953@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3753050.1659102953%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2022-Jul-29, PG Bug reporting form wrote:
>> When executing the following query:
>> (echo "SELECT row("; for ((i=1;i<100001;i++)); do echo "'$i',$i,"; done;
>> echo "'0',0);"; ) | psql
>> I got server crash with the following backtrace

> Hah, of course.  I suppose we'd need something like this ... haven't
> looked for other problem spots.

I think the parser should've prevented this.  It's in charge of
rejecting overlength SELECT lists, for example.  Also, the limit
probably needs to be just MaxTupleAttributeNumber.

			regards, tom lane