Re: [HACKERS] Re: Trouble with float4 afterupgrading from
6.5.3 to 7.0.2
From:
<vectro(at)pipeline(dot)com>
To:
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc:
Philip Warner <pjw(at)rhyme(dot)com(dot)au>,
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>,
Romanenko Mikhail <mikhail(at)angg(dot)ru>, pgsql-general(at)postgresql(dot)org,
pgsql-hackers(at)postgresql(dot)org
Subject:
Re: [HACKERS] Re: Trouble with float4 afterupgrading from
6.5.3 to 7.0.2
> I suppose we could implement the conversion as "float8in(float4out(x))"
> instead of "(double) x" but it'd be several orders of magnitude slower,
> as well as being *less* useful to those who know what they're doing with
> float math (since the result would actually be a less-precise conversion
> except in cases where the intended value has a short decimal
> representation).
We only need to maintain the lower-order bit(s). Seems this could be done
a lot easier than by an ascii in-between.
Is there a reason we can't perform the conversion and then copy the
low-order bits manually, with some bit-shifting and masking?
Ian
