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

From Peter Eisentraut
Subject Re: Remove configure --disable-float4-byval and--disable-float8-byval
Date
Msg-id d139dd8f-691b-5c48-01c7-25247daed7cd@2ndquadrant.com
Whole thread Raw
In response to Re: Remove configure --disable-float4-byval and--disable-float8-byval  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Remove configure --disable-float4-byval and--disable-float8-byval  (Michael Paquier <michael@paquier.xyz>)
Re: Remove configure --disable-float4-byval and--disable-float8-byval  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2019-11-02 08:39, Peter Eisentraut wrote:
> On 2019-10-31 14:36, Tom Lane wrote:
>> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>>> float4 is now always pass-by-value; the pass-by-reference code path is
>>> completely removed.
>>
>> I think this is OK.
> 
> OK, here is a patch for just this part, and we can continue the
> discussion on the rest in the meantime.

I have committed this part.

I will rebase and continue developing the rest of the patches based on 
the discussion so far.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: why doesn't optimizer can pull up where a > ( ... )
Next
From: Pavel Stehule
Date:
Subject: Re: dropdb --force