Re: Proposal to introduce a shuffle function to intarray extension

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Martin Kalcher <martin(dot)kalcher(at)aboutsource(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Proposal to introduce a shuffle function to intarray extension
Date: 2022-07-17 22:53:31
Message-ID: 464381.1658098411@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Seems OK for a worst case. It must still be a lot faster than doing
> it in SQL. Now I wonder what the exact requirements would be to
> dispatch to a faster version that would handle int4.

I find it impossible to believe that it's worth micro-optimizing
shuffle() to that extent. Now, maybe doing something in that line
in deconstruct_array and construct_array would be worth our time,
as that'd benefit a pretty wide group of functions.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martin Kalcher 2022-07-17 23:05:19 Re: Proposal to introduce a shuffle function to intarray extension
Previous Message Tom Lane 2022-07-17 22:46:27 Re: Proposal to introduce a shuffle function to intarray extension

Browse pgsql-hackers by date

  From Date Subject
Next Message Martin Kalcher 2022-07-17 23:05:19 Re: Proposal to introduce a shuffle function to intarray extension
Previous Message Tom Lane 2022-07-17 22:46:27 Re: Proposal to introduce a shuffle function to intarray extension