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 1rOKTE-003HVl-9t for pgsql-bugs@arkaria.postgresql.org; Fri, 12 Jan 2024 16:33:24 +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 1rOKTD-003Jlg-CS for pgsql-bugs@arkaria.postgresql.org; Fri, 12 Jan 2024 16:33: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 1rOKTD-003JlW-4E for pgsql-bugs@lists.postgresql.org; Fri, 12 Jan 2024 16:33:23 +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 1rOKTA-001DRR-PO for pgsql-bugs@lists.postgresql.org; Fri, 12 Jan 2024 16:33:22 +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 40CGXIs5484396; Fri, 12 Jan 2024 11:33:18 -0500 From: Tom Lane To: "Jonathan S. Katz" cc: Michael Paquier , 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: <9115f2e8-8dde-4545-868c-9becb2260aef@postgresql.org> References: <2433182.1702391878@sss.pgh.pa.us> <3453263.1702739958@sss.pgh.pa.us> <1673413.1703442075@sss.pgh.pa.us> <1851211.1703519939@sss.pgh.pa.us> <9115f2e8-8dde-4545-868c-9becb2260aef@postgresql.org> Comments: In-reply-to "Jonathan S. Katz" message dated "Fri, 12 Jan 2024 11:19:08 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <484394.1705077198.1@sss.pgh.pa.us> Date: Fri, 12 Jan 2024 11:33:18 -0500 Message-ID: <484395.1705077198@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Jonathan S. Katz" writes: > On 1/10/24 8:12 PM, Michael Paquier wrote: >> While looking at the whole picture, an issue with the direct removal >> of money is how we should handle btree_gin and btree_gist which have >> operators based on money. We try to keep things compatible at >> run-time, but could this be worth a hard break in these modules, >> dropping the older sql scripts used in the modules if we don't have >> access to money anymore at runtime? These are not popular modules.. >> Any thoughts about that? > Both modules are pretty popular. Yeah, I think it's a serious error to assume they aren't used plenty. Not the money part, but other scalar types. > It sounds like we'd have to tread a bit lightly because of this, even if > money is not frequently (or at all) used with btree_gist/gin? What'd have to happen is that people would have to upgrade to a version of btree_gin/btree_gist that deletes its money support before they could pg_upgrade into a core version that lacks money. So we'd have to ship that version at least one major release before nuking the core support. I think the shortest timeline we could possibly do this on is: v17: label money as deprecated and due for removal in the SGML docs v18: remove support in btree_gin/btree_gist (and any other affected extensions) v19: remove it from core Note that in v18, people could still use money even in btree_gin/btree_gist, just by installing a non-default extension version. So their C code for money would have to stay. regards, tom lane