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 1qTva9-00B9G4-EL for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Aug 2023 02:39:25 +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 1qTva7-00AHSn-GY for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Aug 2023 02:39:23 +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 1qTva7-00AHSf-8k for pgsql-bugs@lists.postgresql.org; Thu, 10 Aug 2023 02:39:23 +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 1qTva5-001bD4-4y for pgsql-bugs@lists.postgresql.org; Thu, 10 Aug 2023 02:39:23 +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:To:From:Date:Sender:Reply-To:Cc: Content-ID:Content-Description; bh=m5WADUlDICH23XzrvWX+jKHSnarkRBIxPVzQyaQWDGM=; b=HRboc78ejMpP6prRMDmMaCKdxx FM1WhMYhytmw28KmI23MhGT2TPCS3zrxb8cvdPti59rXdTPOu4ulmY58EfyiSMHNLMzSKNPTXmMeB ci0aPG5fPTX5UkKwP7PxNakY2EQQ9LUbeUmIxGAJ6VkWrwMfeF79zVn6ffc3+ZmexMEQmQkcOiXSz G0S8kYDZzibmiFxP0fBH9FJgu205r1rCSPQw3oH0wpNOXQo0VL4gDVltzYMc30wLQEKodJbX+L1Ze PHdjuRb1K00j3YhbdLi+QY3CldeJa2OaakHIau1Cd7PJRC88058BV2k/JV6ZooxAl8ryzjnFsua8h gi7pj/Hw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qTva1-00E3xB-1E; Wed, 09 Aug 2023 22:39:17 -0400 Date: Wed, 9 Aug 2023 22:39:17 -0400 From: Bruce Momjian To: msdnchina@163.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate Message-ID: References: <18034-08e668401be826ed@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <18034-08e668401be826ed@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jul 20, 2023 at 03:25:11PM +0000, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 18034 > Logged by: yanliang lei > Email address: msdnchina@163.com > PostgreSQL version: 16beta2 > Operating system: RHEL7.9 > Description: > > in the https://www.postgresql.org/docs/16/release-16.html, there is a new > feature :Accept the spelling "+infinity" in datetime input。 > Actually,"in datetime input " is not accurate. > Actually, in the PostgreSQL 16 beta2 edition, the spelling "+infinity" can > be used in the following three datatypes: > 1.timestamp [ (p) ] [ without time zone ] > 2.timestamp [ (p) ] with time zone > 3.date > > and the spelling "+infinity" can not be used in the following two > datatypes: > 1.time [ (p) ] [ without time zone ] > 2.time [ (p) ] with time zone > > so ,I think that the follow descirtion is accurate: > Accept the spelling "+infinity" in the following data types: > timestamp [ (p) ] [ without time zone ] 、 > timestamp [ (p) ] with time zone、 > date datatypes。 We call our timestamp type datetime in some cases, e.g.: https://www.postgresql.org/docs/16/runtime-config-client.html#RUNTIME-CONFIG-CLIENT-FORMAT timezone_abbreviations (string) Sets the collection of time zone abbreviations that will be accepted by the server for datetime input. I see it in a few other places. Should we rename it other places too? I thought datetime was just a short-hand for our date-time types. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.