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 1qU3ol-00BWJ1-Th for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Aug 2023 11:27:04 +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 1qU3nl-00E2Dm-Jr for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Aug 2023 11:26:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qU3nl-00E2D4-1g for pgsql-bugs@lists.postgresql.org; Thu, 10 Aug 2023 11:26:01 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qU3ne-001Zn5-I1 for pgsql-bugs@lists.postgresql.org; Thu, 10 Aug 2023 11:26:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=xGOe1DazGmk596UFQ4ZAy0dsgHXWRfsJ8xlMn4gVl6w=; b=wMSt5 jmx2ssBCmGoKVQIzmNUB97sRV6ho7tTBON4d34o5qY94FYiwRn4AFsrtsz0/ysQv3H+8/eLgJzbhc OnyikUAVOxCfZEZmK4ig8Hbmy8YL6fyvC+aH+afKuqTOg2htrzhsSNOTsCXawst9TBLM1yvGazR0+ iWOY5gNXfDwn9MynSQMXo+wlDcAWzfCjjaheMzkK1id4k204dCPWQiXc+j2d2NxCvWvad1lg0g2hV X5RYDnB2tGgTz6iw3Ennxr/L4ONnZPPFun1NYXsr2u0w203dBumljVjRn+uXjJU1YxbbntPh7VKqJ l9n37yauW8lW1CV+efxTuAIXUPiOA==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qU3nb-00Fsq6-07; Thu, 10 Aug 2023 07:25:51 -0400 Date: Thu, 10 Aug 2023 07:25:51 -0400 From: Bruce Momjian To: Tom Lane Cc: 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> <26522.1691636007@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26522.1691636007@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Aug 9, 2023 at 10:53:27PM -0400, Tom Lane wrote: > Bruce Momjian writes: > > We call our timestamp type datetime in some cases, e.g.: > > ... > > 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. > > I don't see much reason to change anything here. "Datetime" is not > a perfectly strict classification, eg it might or might not include > "interval" depending on context, and I don't want to try to make > that exact. > > A more specific release note entry could be "Accept the spelling > '+infinity' for datetime types that accept infinity"; but I'm not > sure it's worth the extra verbiage. Yeah, that was my analysis too. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.