Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyg5u-00ABEQ-4r for pgsql-docs@arkaria.postgresql.org; Thu, 02 Nov 2023 22:23:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qyg5q-00FraY-M2 for pgsql-docs@arkaria.postgresql.org; Thu, 02 Nov 2023 22:23:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyg5q-00FraP-ED for pgsql-docs@lists.postgresql.org; Thu, 02 Nov 2023 22:23:14 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyg5h-004OPv-UF for pgsql-docs@lists.postgresql.org; Thu, 02 Nov 2023 22:23:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=Apf97jx0etK6o/lf3nVnNUqf08prNl9vXav4G4xBtlU=; b=XqTjVqrKDEBHJ3+CdZg5VviO6u Y5rqFtifKx/3gDacDn5B66+Tj6J+/kXmMI/HFSRgZFX/01bfoUtuvM9UOcXNEWRYZ7bILgF2S7a59 5P+uIBEMVOutFZJZpH+G3DpmJO77egZcUatc5pMxHN+pk/bvzjRcG8AA9LHp10pIxgA9x7LKEewLZ 1A0ggMCZj07xdYL6BEEygsZrfEuw2Ve5msOI0gkB9WOhor4x2G7M2N+T1ue7NnFBFu6b0538tFg5z jKL/RoFIfKbnAgXXzPrvTJGmGViwgnFHPGPTY+0QiPQYHYiTAXvbEshmQIBtbdBYBpsPQ6yplASgN fVz8VFEw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qyg5b-00D0p8-2E; Thu, 02 Nov 2023 18:22:59 -0400 Date: Thu, 2 Nov 2023 18:22:59 -0400 From: Bruce Momjian To: Laurenz Albe Cc: Fujii Masao , jani.rahkola@iki.fi, pgsql-docs@lists.postgresql.org Subject: Re: Documentation of return values of range functions lower and upper Message-ID: References: <53ec9f116bea9252d7fa9341e024530553656c42.camel@cybertec.at> <16601466752e40543051369fac722c0a200bb4e6.camel@cybertec.at> <27d690d8-0987-5f2b-a2da-fc2ec7c19e3c@oss.nttdata.com> <02f3fa3a592fa6c1f8ec1a9f539ae376f744eb42.camel@cybertec.at> <687683a11c0d8bd0466cedbcb99d098c11f31f97.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <687683a11c0d8bd0466cedbcb99d098c11f31f97.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Nov 2, 2023 at 03:42:53PM +0100, Laurenz Albe wrote: > On Thu, 2023-11-02 at 10:14 -0400, Bruce Momjian wrote: > > Better, though "Is the range's upper bound unbounded?" makes me cringe. > > > > Oh, yeah, totally cringe, me too.  :-) > > > > > It is not the bound that is bounded or not, but the range. > > > > > > How about "Is the range unbounded at the upper end?" or "Does the range > > > have no upper bound?" > > > > I used your "end" idea to modify the patch, attached. > > There are still some loose ends: > > - you lost the specification whether it is the upper or the lower bound > > - "Infinity" is a literal > > - "-Infinity" is a very unlikely value for an upper bound > > How about the attached version? Agreed, yours is much better. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.