Re: BUG #17561: Server crashes on executing row() with very long argument list - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #17561: Server crashes on executing row() with very long argument list
Date
Msg-id 20220729101411.7b45rvhlrsgcajjo@alvherre.pgsql
Whole thread Raw
In response to BUG #17561: Server crashes on executing row() with very long argument list  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17561: Server crashes on executing row() with very long argument list  (Richard Guo <guofenglinux@gmail.com>)
Re: BUG #17561: Server crashes on executing row() with very long argument list  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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
...
> #5  0x0000557e1694f850 in ExceptionalCondition
> (conditionName=conditionName@entry=0x557e169b2e62 "attributeNumber >= 1",
> errorType=errorType@entry=0x557e169b0e7f "BadArgument",
> fileName=fileName@entry=0x557e169b2d7c "tupdesc.c", 
>     lineNumber=lineNumber@entry=598) at assert.c:69
> #6  0x0000557e1642790a in TupleDescInitEntry
> (desc=desc@entry=0x7f42a4c8b050,
> attributeNumber=attributeNumber@entry=-32768,
> attributeName=attributeName@entry=0x0, oidtypeid=23, typmod=typmod@entry=-1,
> attdim=attdim@entry=0)
>     at tupdesc.c:598
> #7  0x0000557e1664c509 in ExecTypeFromExprList (exprList=0x7f42a7830cf0) at
> execTuples.c:2009

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

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/

Attachment

pgsql-bugs by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: BUG #17561: Server crashes on executing row() with very long argument list
Next
From: Richard Guo
Date:
Subject: Re: BUG #17560: Planner can not find plan with lowest cost