Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSILf-0001HF-0a for pgsql-docs@arkaria.postgresql.org; Wed, 06 Nov 2019 10:15:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSILd-0007aa-Ej for pgsql-docs@arkaria.postgresql.org; Wed, 06 Nov 2019 10:15:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSILc-0007aT-Tn for pgsql-docs@lists.postgresql.org; Wed, 06 Nov 2019 10:15:33 +0000 Received: from forward102o.mail.yandex.net ([2a02:6b8:0:1a2d::602]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iSILU-0005HX-KK for pgsql-docs@lists.postgresql.org; Wed, 06 Nov 2019 10:15:31 +0000 Received: from mxback5g.mail.yandex.net (mxback5g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:166]) by forward102o.mail.yandex.net (Yandex) with ESMTP id 413FD6680F25; Wed, 6 Nov 2019 13:15:20 +0300 (MSK) Received: from iva7-f08b2a8dca2b.qloud-c.yandex.net (iva7-f08b2a8dca2b.qloud-c.yandex.net [2a02:6b8:c0c:6e00:0:640:f08b:2a8d]) by mxback5g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id bAwOoWQ4mx-FJRevTAc; Wed, 06 Nov 2019 13:15:20 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1573035320; bh=EftlmcQjE9GHR5Zz7npFIYqZ9HaPqzq2skJeUnEMaXw=; h=In-Reply-To:Subject:CC:To:From:References:Date:Message-ID; b=EmqwKTpgor7kVrtYZ/n4tETeCei/hDosYpNT+Dg7kaBDYy1FacaTGr78BwyJtbYRX dArzI1AWbQemNRI8g9BGlTKuiAn9kScR9nBqXdqdAxF8+Hw/gfzAP4tjMMdM6XzvK2 U3/ktNiJyc94lX5mpHG0gqWOAuBiBbAN2HTCls6k= Authentication-Results: mxback5g.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by iva7-f08b2a8dca2b.qloud-c.yandex.net (nwsmtp/Yandex) with ESMTPSA id spPxdmj0es-FI00HLnr; Wed, 06 Nov 2019 13:15:18 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client certificate not present) Date: Wed, 6 Nov 2019 12:15:17 +0200 From: Eugen Konkov Message-ID: <1254054284.20191106121517@yandex.ru> To: Bruce Momjian CC: Tom Lane , pgsql-docs@lists.postgresql.org Subject: Re: Why 'infinity' is not in range '[2019-01-02, infinity]'? In-Reply-To: <20191106042111.GC16353@momjian.us> References: <155655432452.1371.6115195379691603427@wrigleys.postgresql.org> <5f6b986b-de4d-8a43-1366-fc8c3aed6319@postgresql.org> <1265663903.20190429212216@yandex.ru> <7991.1556573455@sss.pgh.pa.us> <376945611.20191026161529@yandex.ru> <20191106042111.GC16353@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ! Specifying a missing bound as exclusive is automatically converted ! to inclusive, e.g., [,] is automatically converted ! to (,) Misspell? You say: exclusive is automatically converted to inclusive But then: [,] is automatically converted to (,) which one is correct? -- Best regards, Eugen Konkov