From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Wolfgang Walther <walther(at)technowledgy(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Calling variadic function with default value in named notation |
Date: | 2020-11-02 16:22:00 |
Message-ID: | CAKFQuwZ_Eq08_7Uf9EBrBj9UFRnB6nqoe=p1tOg+5Dt4181+uw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Oct 29, 2020 at 8:51 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > As I look at this more I'm definitely agreeing that the documentation
> here
> > is problematic. Specifically, the fact that the only place about this
> > syntax is in a chapter under Extending SQ - SQL Functions, is not good.
> It
> > really needs to be in the Syntax chapter.
>
> The documentation situation was complained of in the 2009 thread I just
> cited :-(. Doesn't look like anybody did anything about it.
>
> I am not, however, persuaded that you can just move a bunch of that
> material to the syntax chapter.
That wasn't the intent, but the exact solution will take time to come up
with so I was just being vague.
I don't think it's very practical
> to describe variadic functions when the user doesn't know how to
> create one.
Plenty of users are able to execute built-in functions without knowing how
to create them. This doesn't seem any different.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Borisov | 2020-11-02 16:55:14 | Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering |
Previous Message | Tom Lane | 2020-11-02 15:02:54 | Re: BUG #16694: Server hangs in 100% CPU loop when decompressing a specific TOAST Postgis linestring |