| From: | Nikhil Benesch <nikhil(dot)benesch(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Sean Loiselle <himself(at)seanloiselle(dot)com> |
| Subject: | Re: Array parsing incorrectly accepts ragged multidimensional arrays |
| Date: | 2023-06-05 01:02:45 |
| Message-ID: | CAPWqQZQmOyj3RPfSQ0jL5=kdON1ngHYWGUvoUw_yZaD0bvsM3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Ah, thanks for the pointer. Funny how these bugs can go unnoticed for
two decades and then get noticed twice in the same month.
On Sun, Jun 4, 2023 at 6:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Nikhil Benesch <nikhil(dot)benesch(at)gmail(dot)com> writes:
> > While working on Postgres-compatible array support in Materialize, my
> > colleague Sean Loiselle (CC'd) discovered what a class of seemingly
> > invalid array values that are accepted by Postgres's array input
> > routine:
>
> Yeah, see existing thread (and patch) at
>
> https://www.postgresql.org/message-id/flat/2794005(dot)1683042087(at)sss(dot)pgh(dot)pa(dot)us
>
> Please review that if you'd like.
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2023-06-05 07:40:42 | Re: BUG #17961: Incorrect aggregation MIN, AVG, MAX |
| Previous Message | Tom Lane | 2023-06-04 22:53:32 | Re: Array parsing incorrectly accepts ragged multidimensional arrays |