| From: | Martin Kalcher <martin(dot)kalcher(at)aboutsource(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Introduce array_shuffle() and array_sample() |
| Date: | 2022-09-29 09:39:28 |
| Message-ID: | c4b69308-fc69-66d5-7905-7c3268833a50@aboutsource.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Am 28.09.22 um 16:18 schrieb Tom Lane:
> It is seeded at process start, yes. If you don't feel a need for
> user control over the sequence used by these functions, then using
> pg_global_prng_state is fine. (Basically the point to be made
> here is that we need to keep a tight rein on what can be affected
> by setseed().)
>
> regards, tom lane
New patch: array_shuffle() and array_sample() use pg_global_prng_state now.
Martin
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Introduce-array_shuffle-and-array_sample.patch | text/x-patch | 10.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lahnov, Igor | 2022-09-29 13:04:08 | RE: Streaming wal from primiry terminating |
| Previous Message | Kyotaro Horiguchi | 2022-09-29 03:02:24 | Re: Streaming wal from primiry terminating |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kuroda.hayato@fujitsu.com | 2022-09-29 09:50:01 | RE: Perform streaming logical transactions by background workers and parallel apply |
| Previous Message | Amit Langote | 2022-09-29 09:18:10 | Re: Eliminating SPI from RI triggers - take 2 |