Re: BUG #17561: Server crashes on executing row() with very long argument list
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #17561: Server crashes on executing row() with very long argument list |
| Дата | |
| Msg-id | 3753050.1659102953@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: BUG #17561: Server crashes on executing row() with very long argument list (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
| Ответы |
Re: BUG #17561: Server crashes on executing row() with very long argument list
Re: BUG #17561: Server crashes on executing row() with very long argument list |
| Список | pgsql-bugs |
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
В списке pgsql-bugs по дате отправления: