From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | kcai(at)wyebot(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: A typo? |
Date: | 2024-04-07 15:11:21 |
Message-ID: | CAKFQuwa1nnxO5wXj=45TZaMaNiF3DdLkSiDe5SOm4-nNKfe30w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Sun, Apr 7, 2024 at 7:24 AM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> On Sun, Apr 7, 2024 at 6:30 PM PG Doc comments form
> <noreply(at)postgresql(dot)org> wrote:
> >
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/16/plpgsql-declarations.html
> > Description:
> >
> > Under 43.3.1, "Notice that we omitted RETURNS real — we could have
> included
> > it, but it would be redundant."
> > Should that be "RETURNS tax" instead of "RETURNS real"?
>
> I think it's related to the plpgsql "RETURNS" and "RETURN" confusion.
> RETURN can appear between "begin", "end".
> RETURNS need to specify before "AS".
>
>
Right, the OP needs to have consulted the CREATE FUNCTION reference page to
find the definition of the RETURNS clause since it is language agnostic.
https://www.postgresql.org/docs/current/sql-createfunction.html
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Behrens | 2024-04-08 12:39:05 | Re: Non-blocking synchronization in libpq using pipeline mode |
Previous Message | Tom Lane | 2024-04-07 15:02:35 | Re: A typo? |