From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] random_normal function |
Date: | 2022-12-22 02:38:50 |
Message-ID: | Y6PDOq83Gs349cE8@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 21, 2022 at 08:47:32AM +0100, Fabien COELHO wrote:
> From a typical use case point of view, I'd say uniform, normal and
> exponential would make sense for floats. I'm also okay with generating a
> uniform bytes pseudo-randomly.
I'd agree with this set.
> I'd be more at ease to add simple functions rather than a special
> heavy-on-keywords syntax, even if standard.
Okay.
>> Note that SQLValueFunction made the addition of more returning data
>> types a bit more complicated (not much, still) than the new
>> COERCE_SQL_SYNTAX by going through a mapping function, so the
>> keyword/function mapping is straight-forward.
>
> I'm unclear about why this paragraph is here.
Just saying that using COERCE_SQL_SYNTAX for SQL keywords is easier
than the older style. If the SQL specification mentions no SQL
keywords for such things, this is irrelevant, of course :)
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2022-12-22 02:54:28 | Re: Inconsistency in reporting checkpointer stats |
Previous Message | Richard Guo | 2022-12-22 02:37:35 | Re: Optimization issue of branching UNION ALL |