Re: [PATCHES] guc - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCHES] guc
Date
Msg-id Pine.LNX.4.30.0201180038480.725-100000@peter.localdomain
Whole thread Raw
In response to Re: [PATCHES] guc  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Geometric types (was Re: [PATCHES] guc)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> Indeed.  Does that mean you'd be happy with restricting the number of
> digits printed for geometrical types only?

Not really.  I'd much rather see the EPSILON removed/revised.  I don't
claim to understand numerical analysis, but that thing is completely
bogus.  I can see how the error would be controllable when you just add
numbers, but once you start multiplying or run trigonometric functions, a
fixed epsilon just doesn't cut it.

If you want to limit the number of digits, why not just reimplement the
geometric types as single precision?

And if we think that an epsilon-based float comparison is important, why
don't we do it everywhere?

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: tuptoaster.c must *not* use SnapshotAny
Next
From: Bruce Momjian
Date:
Subject: Re: tuptoaster.c must *not* use SnapshotAny