Re: Remove configure --disable-float4-byval and --disable-float8-byval - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Remove configure --disable-float4-byval and --disable-float8-byval
Date
Msg-id CAH2-Wzn_Qb4T1gM9QqYPFEkUaDAd-_XvR5c_2V-gaRt6bjQmzA@mail.gmail.com
Whole thread Raw
In response to Re: Remove configure --disable-float4-byval and--disable-float8-byval  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Remove configure --disable-float4-byval and--disable-float8-byval  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Fri, Nov 1, 2019 at 7:47 PM Michael Paquier <michael@paquier.xyz> wrote:
> > 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.
>
> I don't agree as well with the line of arguments to just remove 32b
> support.

Clearly you didn't read what I actually wrote, Michael.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Remove configure --disable-float4-byval and--disable-float8-byval
Next
From: Michael Paquier
Date:
Subject: Re: [BUG] Partition creation fails after dropping a column andadding a partial index