Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1igZy1-0004A7-5i for pgsql-hackers@arkaria.postgresql.org; Sun, 15 Dec 2019 19:54:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1igZxz-0008Nc-Vh for pgsql-hackers@arkaria.postgresql.org; Sun, 15 Dec 2019 19:54:11 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1igZxz-0008NV-MV for pgsql-hackers@lists.postgresql.org; Sun, 15 Dec 2019 19:54:11 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1igZxx-0006qL-87 for pgsql-hackers@postgresql.org; Sun, 15 Dec 2019 19:54:11 +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 xBFJs3TU027169; Sun, 15 Dec 2019 14:54:03 -0500 From: Tom Lane To: Thomas Munro cc: Laurenz Albe , Jim Finnerty , pgsql-hackers Subject: Re: On disable_cost In-reply-to: References: <20191101160038.wn3qkvp4psnatmm3@alap3.anarazel.de> <1572625852934-0.post@n3.nabble.com> <20191101170406.w6ybnafyvpxv2ltg@development> <30025.1572707098@sss.pgh.pa.us> <1576018229539-0.post@n3.nabble.com> <6da76620383a421c2f4164bd314bab9499d2ec5c.camel@cybertec.at> Comments: In-reply-to Thomas Munro message dated "Fri, 13 Dec 2019 15:59:32 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27167.1576439643.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 15 Dec 2019 14:54:03 -0500 Message-ID: <27168.1576439643@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Thomas Munro writes: > On Wed, Dec 11, 2019 at 7:24 PM Laurenz Albe = wrote: >> Doesn't that rely on a specific implementation of double precision (IEE= E)? >> I thought that we don't want to limit ourselves to platforms with IEEE = floats. > Just by the way, you might want to read the second last paragraph of > the commit message for 02ddd499. The dream is over, we're never going > to run on Vax. Still, the proposed hack is doubling down on IEEE dependency in a way that I quite dislike, in that (a) it doesn't just read float values but generates new ones (and assumes that the hardware/libc will react in a predictable way to them), (b) in a part of the code that has no damn business having close dependencies on float format, and (c) for a gain far smaller than what we got from the Ryu code. We have had prior discussions about whether 02ddd499 justifies adding more IEEE dependencies elsewhere. I don't think it does. IEEE 754 is not the last word that will ever be said on floating-point arithmetic, any more than x86_64 is the last CPU architecture that anyone will ever care about. We should keep our dependencies on it well circumscribed. regards, tom lane