Re: general purpose array_sort

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Junwang Zhao <zhjwpku(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, "andreas(at)proxel(dot)se" <andreas(at)proxel(dot)se>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: general purpose array_sort
Date: 2025-03-16 13:49:58
Message-ID: CACJufxEDqZraG+ZbKk6R=+0SODrkERpjhTD9yb69YTfJi=-UOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

hi.

before commit 4618045bee4a6d3efcb489c319649d8dd9aaa738 ([0])

select array_sort(array(select '1 4'::int2vector union all select '1
2'::int2vector));
array_sort
--------------------------
[1:2][0:1]={{1,2},{1,4}}
(1 row)

after

select array_sort(array(select '1 4'::int2vector union all select '1
2'::int2vector));
array_sort
---------------
{"1 2","1 4"}
(1 row)

now look closer, the second is the expected result...
I didn't dig deeper why commit 4618045bee made this patch result correct,
but I guess it would be best to include such a test case,
so I've attached a patch.

[0] https://git.postgresql.org/cgit/postgresql.git/commit/?id=4618045bee4a6d3efcb489c319649d8dd9aaa738

Attachment Content-Type Size
v17-0002-general-purpose-array_sort.patch text/x-patch 8.6 KB
v17-0001-general-purpose-array_sort.patch text/x-patch 16.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Roberto Mello 2025-03-16 15:04:12 Re: PATCH: warn about, and deprecate, clear text passwords
Previous Message Daniel Gustafsson 2025-03-16 13:48:58 Re: Adding support for SSLKEYLOGFILE in the frontend