Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eOsOf-0001Tt-EF for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Dec 2017 21:47:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eOsOf-0006c9-1r for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Dec 2017 21:47:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eOsOe-0006bz-Ri for pgsql-hackers@lists.postgresql.org; Tue, 12 Dec 2017 21:47:28 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eOsOX-0004D7-Cy for pgsql-hackers@postgresql.org; Tue, 12 Dec 2017 21:47:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id vBCLlHIq025616; Tue, 12 Dec 2017 16:47:17 -0500 From: Tom Lane To: Andres Freund cc: Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: money type's overflow handling is woefully incomplete In-reply-to: <20171212182153.wm7qrwfsfigciuck@alap3.anarazel.de> References: <20171211225032.2phzzekso4337xmy@alap3.anarazel.de> <1420.1513094464@sss.pgh.pa.us> <20171212182153.wm7qrwfsfigciuck@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 12 Dec 2017 10:21:53 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25614.1513115237.1@sss.pgh.pa.us> Date: Tue, 12 Dec 2017 16:47:17 -0500 Message-ID: <25615.1513115237@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: >> Robert Haas writes: >>> Long story short, I don't think anyone cares about this enough to >>> spend effort fixing it. I suspect the money data type has very few >>> users. > I'm unfortunately not so sure :(. There seem to be enough of them that we get pushback anytime somebody suggests removing the type. > The background is that I was working on committing the faster (& > correct) overflow checks, and wanted to compile postgres with -ftrapv. > Some rudimentary cash (as well as pgbench, rel/abstime) fixes were > required to make the tests succeed... Really? We've got test cases that intentionally exercise overflow in the money code? I think we could just drop such tests, until such time as someone fixes the issue. (OTOH, I bet we could drop reltime/abstime without too many complaints. Y2038 is coming.) regards, tom lane