| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martin Kalcher <martin(dot)kalcher(at)aboutsource(dot)net> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, 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 03:37:26 |
| Message-ID: | 4077925.1658029046@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
I wrote:
> On the whole, I'd vote for calling it shuffle(), and expecting that
> we'd also use that name for any future generic version.
Actually ... is there a reason to bother with an intarray version
at all, rather than going straight for an in-core anyarray function?
It's not obvious to me that an int4-only version would have
major performance advantages.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2022-07-17 06:00:09 | Re: Proposal to introduce a shuffle function to intarray extension |
| Previous Message | David G. Johnston | 2022-07-17 03:36:48 | Re: Proposal to introduce a shuffle function to intarray extension |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2022-07-17 03:59:57 | Re: optimize lookups in snapshot [sub]xip arrays |
| Previous Message | David G. Johnston | 2022-07-17 03:36:48 | Re: Proposal to introduce a shuffle function to intarray extension |