From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Subject: | Re: proposal: variadic argument support for least, greatest function |
Date: | 2019-03-11 17:04:42 |
Message-ID: | 4cad2f09-22d6-379b-8026-9d208c3e7aab@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/11/19 6:43 PM, Andrew Dunstan wrote:
>
> On 3/6/19 10:24 AM, Chapman Flack wrote:
>> On 3/6/19 10:12 AM, Andrew Dunstan wrote:
>>
>>> Having reviewed the thread, I'm with Andres and Tom. Maybe though we
>>> should have a note somewhere to the effect that you can't use VARIADIC
>>> with these.
>> Perhaps such a note belongs hoisted into the functions-conditional
>> section of the manual, making a general observation that these things
>> are conditional *expressions* that may resemble functions, but in
>> particular, COALESCE, GREATEST, and LEAST cannot be called with
>> keyword VARIADIC and an array argument, as they could if they were
>> ordinary functions.
>>
>
>
> I'm going to mark this as rejected. Here's a possible doc patch
+1
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2019-03-11 17:20:21 | Re: pgbench MAX_ARGS |
Previous Message | Dagfinn Ilmari Mannsåker | 2019-03-11 17:04:03 | Re: pgbench MAX_ARGS |