From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org> |
Subject: | Re: array_random |
Date: | 2025-07-11 07:49:09 |
Message-ID: | CAEZATCU8s3M2R6LALz6aZL_4bVSoDk_zwZ52JjM=t6dXSJCh3g@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 8 Jul 2025 at 15:26, Aleksander Alekseev
<aleksander(at)tigerdata(dot)com> wrote:
>
> The proposed function seems to do two things at a time - generating
> random values and transforming them into an array of desired
> dimensions. Generally we try to avoid such interfaces. Can you think
> of something like array_transform() / array_reshape() that takes an
> arbitrary single-dimension array and modifies it?
That's a good point. Arguably, creating a simple 1-D array of random
values is trivial enough to leave to users, and there isn't sufficient
demand to justify creating core functions for it.
OTOH, creating multi-dimensional arrays (of any values, not just
random) is harder. Perhaps there is an argument for in-core functions
to make that easier, though I'm not sure how many people actually use
multi-dimensional arrays. In any case, that seems like a separate
discussion for a new thread, if there's demand.
Regards,
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2025-07-11 08:16:43 | track needed attributes in plan nodes for executor use |
Previous Message | Dean Rasheed | 2025-07-11 07:09:19 | Re: Fix replica identity checks for MERGE command on published table. |