Andrew Dunstan napsal(a):
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
But the question is if the "-fast" flag is good for postgres. The
-fast flag sets "brutal" floating point optimization and some
operation should have less precision. Is possible verify that
floating point operation works well?
That's a pretty good way to guarantee that you'll break the datetime
code.
! | @ 6 years | @ 5 years 12 mons 5 days 6 hours
Doesn't this look odd regardless of what bad results come back from the
FP library?
The problem was generated, because -fast option was set only for the
compiler and not for the linker. Linker takes wrong version of
libraries. If -fast is set for both then horology test is OK, but
question was if float optimalization should generate some problems.
regards, Zdenek
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
