Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
Date: 2023-05-04 15:26:58
Message-ID: 3410202.1683214018@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alexander Lakhin <exclusion(at)gmail(dot)com> writes:
> I continue watching the array handling bugs dancing Sirtaki too. Now it's
> another asymmetry:
> select '{{1},{{2}}}'::int[];
>  {{{1}},{{2}}}
> but:
> select '{{{1}},{2}}'::int[];
>  {}

For the sake of the archives --- this issue in the core code
is being tracked at

https://www.postgresql.org/message-id/2794005.1683042087%40sss.pgh.pa.us

I think all the reported issues in plperl and plpython are resolved now.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message BO ST 2023-05-04 15:51:03 Bug:Create a table with 1600 fields (reaching the upper limit), then drop several fields and create new ones, but the addition failed.
Previous Message Tom Lane 2023-05-04 13:27:49 Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array