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

From Francisco Olarte
Subject Re: BUG #17561: Server crashes on executing row() with very long argument list
Date
Msg-id CA+bJJbxmaTvQ_a1G6r73SZN-mpES5dHW9Ucf0z71ZWk6iQvcDw@mail.gmail.com
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>)
List pgsql-bugs
Egor:

On Fri, 29 Jul 2022 at 11:42, PG Bug reporting form
<noreply@postgresql.org> wrote:
...
Your query generating script.
> 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
.. Does not seem to match the query in your BT...
.....
>     query_string=query_string@entry=0x7f42aace4050 "SELECT
>
row_to_json(row(\n'1',1,\n'2',2,\n'3',3,\n'4',4,\n'5',5,\n'6',6,\n'7',7,\n'8',8,\n'9',9,\n'10',10,\n'11',11,\n'12',12,\n'13',13,\n'14',14,\n'15',15,\n'16',16,\n'17',17,\n'18',18,\n'19',19,\n'20',20,\n'21',21,\n'22',"...,

Although it seems it the extra row_to_json should not matter.

FOS.



pgsql-bugs by date:

Previous
From: Peter Smith
Date:
Subject: Re: Excessive number of replication slots for 12->14 logical replication
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17561: Server crashes on executing row() with very long argument list