"Ian C. Sison" <[EMAIL PROTECTED]> writes:
> We've encountered problems using PGSQL on 7.0.2 and 7.0.3 - I think the
> details below give a good enough overview...
investigating ...
>
> Bottom line: get rid of -fast-math in the gcc options (at least for PGSQL
> recompilation). At least that's what the people in the PGSQL list
> suggested. We're recompiled pgsql here without the fast-math option, and
> confirmed that it solved the problem.
ok, will be fixed soon ...
>
> In the interest of stability, maybe you can include this as an update?
>
>
>
> =========================================
>
> >> >> ERROR: copy: line 3910, Bad timestamp external representation
> >> >> '2000-01-05 00:00:60.00+08'
> >> >> Weird because those timestamps were generated by default now().
> ...
> >> Is there a work-around to this aside from manually changing the dump
> >file?
> >> Distribution Version: Linux Mandrake release 7.2 (Odyssey) for
> >> i586
> >> It was shipped with Mandrake-Linux 7.2
> >> >> migrate=# select version();
> >> >> version
> >> >> ---------------------------------------------------------------
> >> >> PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.95.3
> ...
> >> We can be sure that the compiler is relatively bug free because it was
> >> used to recompile the entire Linux distribution...
>
> Ah ha (or rather, ha ha ha)! I'd suggest using the RPMs posted on the
> postgresql.org ftp site, which include a sample .rpmrc file which fixes
> disasterous bugs in Mandrake's default compiler settings for building
> RPMs. Specifically, Mandrake sets the -ffast-math flag, which the gcc
> folks warn is not compatible with -On optimizations. When I build RPMs I
> kill the fast-math option, and the rounding troubles go away.
>
> The rounding trouble does not show up on other platforms or Linux
> distros because no one else ignores the gcc recommendations to this
> extent :(
>
> - Thomas
