From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net> |
Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: proposal: variadic argument support for least, greatest function |
Date: | 2019-03-11 19:47:12 |
Message-ID: | CAFj8pRC_+1XjswbUtqYLrDQMCMAF_2JUxLeKWnR2sengsTJA=A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
po 11. 3. 2019 v 18:04 odesílatel David Steele <david(at)pgmasters(dot)net> napsal:
> 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
>
>
ok
Pavel
--
> -David
> david(at)pgmasters(dot)net
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-03-11 19:57:03 | Re: monitoring CREATE INDEX [CONCURRENTLY] |
Previous Message | Alvaro Herrera | 2019-03-11 19:43:22 | Re: monitoring CREATE INDEX [CONCURRENTLY] |