| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: array_random |
| Date: | 2025-07-05 07:32:24 |
| Message-ID: | 9bc75fa0-b7ba-4088-909b-b074b6de6f8f@postgresfriends.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30/06/2025 17:04, jian he wrote:
> reasons for adding array_random is:
> 1. This is better than array_fill. This can fill random and constant
> values (random, min and max the same).
> 2. Building a multi-dimensional PL/pgSQL function equivalent to
> array_random is not efficient and is also not easier.
I am not against this at all, but what is the actual use case?
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2025-07-05 08:07:46 | Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL |
| Previous Message | Cédric Villemain | 2025-07-05 07:09:00 | Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach |