| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: intarray sort returns wrong result |
| Date: | 2024-11-12 01:13:44 |
| Message-ID: | 1079628.1731374024@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Junwang Zhao <zhjwpku(at)gmail(dot)com> writes:
> While working on general array sort[1], I played with intarray
> extension, found a bug (or at least inconsistency) when sorting
> multidimensional int array:
> create extension intarray;
> select sort('{{1,2,3}, {2,3,4}}');
> this returns {{1,2,2},{3,3,4}} instead of {{1,2,3},{2,3,4}}
This is documented, isn't it?
Many of these operations are only sensible for one-dimensional
arrays. Although they will accept input arrays of more dimensions,
the data is treated as though it were a linear array in storage
order.
I don't think anyone will thank us for changing intarray's behavior
many years after the fact.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2024-11-12 01:16:37 | Optimizing FastPathTransferRelationLocks() |
| Previous Message | Junwang Zhao | 2024-11-12 00:58:08 | intarray sort returns wrong result |