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 1iQbDj-0000dh-1B for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Nov 2019 18:00:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iQbDh-0005I0-Nv for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Nov 2019 18:00:21 +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 1iQbDh-0005Hh-Ej for pgsql-hackers@lists.postgresql.org; Fri, 01 Nov 2019 18:00:21 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iQbDe-00036D-Qu for pgsql-hackers@postgresql.org; Fri, 01 Nov 2019 18:00:21 +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 xA1I0A7C015315; Fri, 1 Nov 2019 14:00:10 -0400 From: Tom Lane To: Peter Geoghegan cc: Robert Haas , Peter Eisentraut , pgsql-hackers Subject: Re: Remove configure --disable-float4-byval and --disable-float8-byval In-reply-to: References: <15316.1572528990@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Fri, 01 Nov 2019 08:22:27 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15313.1572631210.1@sss.pgh.pa.us> Date: Fri, 01 Nov 2019 14:00:10 -0400 Message-ID: <15314.1572631210@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Peter Geoghegan writes: > On Fri, Nov 1, 2019 at 7:41 AM Robert Haas wrote: >> Could we get around this by making Datum 8 bytes everywhere? > I really like that idea. > Even Raspberry Pi devices (which can cost as little as $35) use 64-bit > ARM processors. It's abundantly clear that 32-bit platforms do not > matter enough to justify keeping all the SIZEOF_DATUM crud around. This line of argument seems to me to be the moral equivalent of "let's drop 32-bit support altogether". I'm not entirely on board with that. Certainly, a lot of the world is 64-bit these days, but people are still building small systems and they might want a database; preferably one that hasn't been detuned to the extent that it barely manages to run at all on such a platform. Making a whole lot of internal APIs 64-bit would be a pretty big hit for a 32-bit platform --- more instructions, more memory consumed for things like Datum arrays, all in a memory space that's not that big. It seems especially insane to conclude that we should pull the plug on such use-cases just to get rid of one obscure configure option. If we were expending any significant devel effort on supporting 32-bit platforms, I might be ready to drop support, but we're not. (Robert's proposal looks to me like it's actually creating new work to do, not saving work.) regards, tom lane