Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fxJ0X-0005fA-HL for pgsql-docs@arkaria.postgresql.org; Tue, 04 Sep 2018 21:37:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fxJ0V-00013O-GE for pgsql-docs@arkaria.postgresql.org; Tue, 04 Sep 2018 21:37:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fxJ0V-00013H-8M for pgsql-docs@lists.postgresql.org; Tue, 04 Sep 2018 21:37:07 +0000 Received: from mail-qk1-x744.google.com ([2607:f8b0:4864:20::744]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fxJ0Q-0008O5-Ms for pgsql-docs@postgresql.org; Tue, 04 Sep 2018 21:37:06 +0000 Received: by mail-qk1-x744.google.com with SMTP id d15-v6so3535647qkc.1 for ; Tue, 04 Sep 2018 14:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=crjL3jSAKGVmk+Cmvt4W9jG5IDpr+NwMypyQeH3Nqag=; b=Eb2Jz0YT/bfLmuOrEwO4Nro1a/wNKxZXYNZxfR5wKgmGCqdyroJk04WrVdGHPboEKs 8c8y0VNuE0/KBf3EpBFP84FZv9Q2rBQ2pWv73QXXFOm+yQy7CaNdjOM9fr1IgxHuN+ad bVFAEbUUTXn0QucVChz9qTony2Z/QMQVTfbm0uRHnX3HiEP11fy/wZIscD15D5PirfSj YE8WlfN0e2vrQ51wTGbwtrZPOed4L/wLgwpGJueGtmmpp0OzJ/iJeS6dnSitTqqVHASa R2qchik6yYzC8qEpvha8HusooIi/K56VW9Ncxj7QMgap1xxPd84ddzsINL4V5k8osa8r iSKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=crjL3jSAKGVmk+Cmvt4W9jG5IDpr+NwMypyQeH3Nqag=; b=f8xC66hM+lsQkXc2DH3Ui7k1frkhT4DYP1rqut3H4Y1RoHxGsxNB3FBv3EgyDYWoa4 roU8FxSGPnFp0psR5C/86d7jNBnQ/b/hKqDf9aYNkVJ7BTuZUNWdD7Blv1DRZE2PcuSv 6xyb87YYrW3mhp1ByIt+iVpXuM4iYjPgsU1bctKI8E6QhvMLFJWvDlFAwEb45mcEgLEe fI5VihQJk3LC/MuYpQbpxKyFU/bS7LU1FSwqi0hW+bXt9KpFAke5U9Rvkjem5+76fDnZ dx8g/S0QddFAGQ2o1QW4xmL81JAPk0ysuIVEGBbx20S82dZjq1Sk0Cy9i+3R3TY7+ovk 76gw== X-Gm-Message-State: APzg51AoMxUnKd1DTcLi9iBNf8P+91gqUf4bSUuIAhRl8es7CIydwzkO RyBiHZpbiTFw2f+9PfZz13DHk5oVfuATslQ/W9I= X-Google-Smtp-Source: ANB0Vdaz5Is6C7ugKhm7UDRBM01dc3Q/hmf8anTx1xY3fjJbhaeGpf2eNG3N8QJ7dFcJyc4HMtdWovDaZKEWnWo8g2k= X-Received: by 2002:a37:5f03:: with SMTP id t3-v6mr29766827qkb.193.1536097019807; Tue, 04 Sep 2018 14:36:59 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a0c:bf98:0:0:0:0:0 with HTTP; Tue, 4 Sep 2018 14:36:59 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Tue, 4 Sep 2018 14:36:59 -0700 Message-ID: Subject: Re: Documentation for alternate names of functions To: Daniel Cory Cc: "pgsql-docs@postgresql.org" Content-Type: multipart/alternative; boundary="00000000000034cbd105751275a9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000034cbd105751275a9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Sep 4, 2018 at 2:17 PM, Daniel Cory wrote: > Can we document that =E2=80=9Cpow=E2=80=9D is the same as =E2=80=9Cpower= =E2=80=9D? It is not listed on > https://www.postgresql.org/docs/current/static/functions-math.html, even > though both =E2=80=9Cceil=E2=80=9D and =E2=80=9Cceiling=E2=80=9D are list= ed. > > For aliased function names for which only one is SQL standard we should denote which one. This particular alias seems worthy of inclusion. > > > Can we document =E2=80=9Cint4larger=E2=80=9D and related functions? They = are similar to > the greatest/least functions but not listed on https://www.postgresql.org= / > docs/current/static/functions-conditional.html#FUNCTIONS-GREATEST-LEAST > I don't see the point of exposing this implementation detail when the greatest/least expressions (i.e., they don't appear under \df), though non-standard, are what users are encouraged to use. Not sure we'd turn down a patch but its not something I'd expect to get picked up in a timely fashion. David J. --00000000000034cbd105751275a9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Se= p 4, 2018 at 2:17 PM, Daniel Cory <dcory@tableau.com> wrote:

Can we document that =E2=80=9Cpow=E2=80=9D is the sa= me as =E2=80=9Cpower=E2=80=9D? It is not listed on https://www.postgresql.org/docs/current/static/f= unctions-math.html, even though both =E2=80=9Cceil=E2=80=9D and = =E2=80=9Cceiling=E2=80=9D are listed.

F= or aliased function names for which only one is SQL standard we should deno= te which one.=C2=A0 This particular alias seems worthy of inclusion.
<= div class=3D"gmail_default" style=3D"font-size:small;background-color:rgb(2= 55,255,255);text-decoration-style:initial;text-decoration-color:initial">
=C2=A0
<= div class=3D"m_-68340697105327729WordSection1">

=C2= =A0

Can we document =E2=80=9Cint4larger=E2=80=9D and rel= ated functions? They are similar to the greatest/least functions but not li= sted on https://www.postgresql.org/docs/current/static/functions-conditio= nal.html#FUNCTIONS-GREATEST-LEAST


I don't see the point of exposing this implementation det= ail when the greatest/least expressions (i.e., they don't appear under = \df), though non-standard, are what users are encouraged to use.=C2=A0 Not = sure we'd turn down a patch but its not something I'd expect to get= picked up in a timely fashion.

David J.

<= /div>
--00000000000034cbd105751275a9--