Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bAVvS-00061V-Nx for pgsql-docs@arkaria.postgresql.org; Wed, 08 Jun 2016 05:21:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bAVvS-0001fV-9s for pgsql-docs@arkaria.postgresql.org; Wed, 08 Jun 2016 05:21:10 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bAVv5-0001FI-Sm for pgsql-docs@postgresql.org; Wed, 08 Jun 2016 05:20:48 +0000 Received: from mail-vk0-x22b.google.com ([2607:f8b0:400c:c05::22b]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bAVv2-0008NL-LB for pgsql-docs@postgresql.org; Wed, 08 Jun 2016 05:20:46 +0000 Received: by mail-vk0-x22b.google.com with SMTP id g67so10546067vkb.3 for ; Tue, 07 Jun 2016 22:20:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=STmYG+KFUWqO5TO7HceCrLTsOrXZlz4zKXq9TgDlCdg=; b=ixcs7UYLq32T5L4kPTTRIOM4TagkTymAJ1q6mALP6VFiq2xBm/CYikmm9D6MH2OF4k TfoLIWqraOcFNiMOCj+9YpvTMO8aA+3P7UpCt+NolggioIG6ClUwX4S/Hq3zhTdJbpfh PZ1rRsyY6f/U1vH2NHrPSyVuwZFpUpjm4ZR6c5pWcCP77RzNT2S5pxxXFu+oqD+sBDi8 FxyG5N2xN73b0hfTlwZkJ4SFpQehEet4kofZL787phyebzMaTLERj/rmtuT1czmFAArY ux2Ox6+TmAwN5PxCB4svS9pJho9RqZH0lXaKh6EUPZof1hO2vjyMsuhXSLHzzUB/gezw PFfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=STmYG+KFUWqO5TO7HceCrLTsOrXZlz4zKXq9TgDlCdg=; b=fHcYjuOwWsVqxPTkKJs5/ZRjOa7oIgWPNAw4NQPIVHAvmc1E6saxL/jLUzi6pCF6RW ZENRe8Hnl9bLGMY1KQ8s0DAf2pssL+fAgoJMtKOzRGZSmUSyO7Iy8oWgt5nIMIUl4Iw2 yvao9vpAlBkNR8VLpdXMBJcRam4aW3nFAWUr3WTn105X55GGU/ltbmfav6zjtcUUAr4L AN33Do2230egYbray3yx2kXoRtkSQqiNQndHiPUqxNTyK8rZNtLYWniyjBxB6MA0fxBs D0YWMBMpSzF8h8YI/RLtvkeo/mfwH3JpuMjFUwJEm1AbZIu0+VmKvndbrIPli8hMvcgl iABg== X-Gm-Message-State: ALyK8tKWOys9KJEE0WChWLm/tkdzeBtkxKtzlTixNaBY1rbNLprQfAuzNjpPN0EAzTGQWxW8rTfkqoZjHDOPag== X-Received: by 10.176.6.230 with SMTP id g93mr1406909uag.50.1465363243697; Tue, 07 Jun 2016 22:20:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.37.42 with HTTP; Tue, 7 Jun 2016 22:20:42 -0700 (PDT) In-Reply-To: <20160607231148.GA512061@alvherre.pgsql> References: <25461.1465330273@sss.pgh.pa.us> <20160607231148.GA512061@alvherre.pgsql> From: Dean Rasheed Date: Wed, 8 Jun 2016 06:20:42 +0100 Message-ID: Subject: Re: Math function description issue To: Alvaro Herrera Cc: Tom Lane , =?UTF-8?Q?J=C3=BCrgen_Purtz?= , pgsql-docs@postgresql.org Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 8 June 2016 at 00:11, Alvaro Herrera wrote: > Tom Lane wrote: >> =?UTF-8?Q?J=c3=bcrgen_Purtz?= writes: > >> > a) In my opinion this wording is easier to understand because it avoids >> > the negation via "not less". >> >> That's a fair point. >> >> The other difference is least/greatest versus smallest/largest. I'm not >> sure if using least/greatest would help the people who misunderstand >> "smallest" as "closest to zero". They might; but being less-common words, >> they might also confuse people whose native language isn't English. >> Anyone have an opinion about which to use? > > As a non-native, the use of "least/greatest" makes it more explicit that > it refers to arithmetic inequality, whereas "smallest" sounds like it > may be related to absolute value comparisons. It's true that > least/greatest are less common words, but that makes it more likely that > they would be looked up in a dictionary, whereas with smallest/largest > people might stick to intuitive knowledge and get them wrong. > Matlab just uses "nearest" for both floor() and ceil(), e.g. "the nearest integer less than or equal to ...". To me, that seems clearer than smallest/largest or least/greatest because you don't have to think about which set of numbers it's trying to exclude. When thinking about the nearest integer, you only have to think about at most 2 possible values. Regards, Dean -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs