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 1rEWSv-00654e-H6 for pgsql-bugs@arkaria.postgresql.org; Sat, 16 Dec 2023 15:20:33 +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 1rEWRt-00CCrL-99 for pgsql-bugs@arkaria.postgresql.org; Sat, 16 Dec 2023 15:19:29 +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 1rEWRt-00CCrD-0g for pgsql-bugs@lists.postgresql.org; Sat, 16 Dec 2023 15:19:29 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rEWRn-00CJOW-2y for pgsql-bugs@lists.postgresql.org; Sat, 16 Dec 2023 15:19:27 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 3BGFJILp3453264; Sat, 16 Dec 2023 10:19:18 -0500 From: Tom Lane To: Michael Paquier cc: David Rowley , exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends In-reply-to: References: <18240-c5da758d7dc1ecf0@postgresql.org> <2171714.1702307153@sss.pgh.pa.us> <2433182.1702391878@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Sat, 16 Dec 2023 10:19:22 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3453262.1702739958.1@sss.pgh.pa.us> Date: Sat, 16 Dec 2023 10:19:18 -0500 Message-ID: <3453263.1702739958@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Tue, Dec 12, 2023 at 09:37:58AM -0500, Tom Lane wrote: >> ... Perhaps we could allow extension >> modules to use binary_upgrade_set_next_pg_type_oid, and then somehow >> reserve the money and _money OIDs forever? > Now, I am not sure that we're making users a favor in keeping around a > data type that's kind of obsolete these days, particularly when all of > them basically require handling of fractional cents when doing serious > calculations. That's a trap in disguise, even if tying data to a > locale for the unit sounds appealing for some applications. Yeah, I wouldn't propose this if money were the only type we were thinking of getting rid of; likely not worth the trouble. But I've got one eye on the geometric types as well --- I think it would be great all around if we could kick those out of the core distribution and let them be maintained independently. But I fear we can't do that without some method whereby pg_upgrade is still possible across the change. regards, tom lane