Re: [HACKERS] Re: Trouble with float4 after upgrading from 6.5.3 to 7.0.2

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 after upgrading from 6.5.3 to 7.0.2
Date: 2000-08-07 16:04:54
Message-ID: 398EDE26.D1547C98@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> Perhaps the old way of considering equality only to float accuracy
> is more useful, even though it opens us up to problems like overflow
> errors in "float4var = 1e100". Comments anyone?

I would not have anticipated this either. I agree that downconverting to
float4 is the right solution.

Possible overflow errors can be checked in advance using the macros or
routines already there. This may be an example of why those could be A
Good Thing in some instances.

- Thomas

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-08-07 16:11:48 Re: [HACKERS] Re: Trouble with float4 after upgrading from 6.5.3 to 7.0.2
Previous Message Philip Warner 2000-08-07 15:57:18 Re: [HACKERS] Re: Trouble with float4 after upgrading from 6.5.3 to 7.0.2

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-08-07 16:11:48 Re: [HACKERS] Re: Trouble with float4 after upgrading from 6.5.3 to 7.0.2
Previous Message Thomas Swan 2000-08-07 16:01:36 UNIONS