Re: proposal: variadic argument support for least, greatest function

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Chapman Flack <chap(at)anastigmatix(dot)net>, David Steele <david(at)pgmasters(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 16:43:25
Message-ID: 9c3525e1-82bd-18b8-d3bc-6f8c14003b59@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
conditional-variadic-doc.patch text/x-patch 671 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2019-03-11 16:43:51 Re: [HACKERS] advanced partition matching algorithm for partition-wise join
Previous Message Alvaro Herrera 2019-03-11 16:27:47 Re: move hash_any to utils/hash/hashfn.c