Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id eAUGmut40856 for ; Thu, 30 Nov 2000 11:48:56 -0500 (EST) (envelope-from pgsql-sql-owner@postgresql.org) Received: from w148.z064003068.lax-ca.dsl.cnc.net (w148.z064003068.lax-ca.dsl.cnc.net [64.3.68.148]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAR7uet30743 for ; Mon, 27 Nov 2000 02:56:40 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1]) by w148.z064003068.lax-ca.dsl.cnc.net (Postfix) with ESMTP id 38FDC17C5E; Mon, 27 Nov 2000 08:16:42 +0000 (UTC) Message-ID: <3A22186A.8A21A9D5@alumni.caltech.edu> Date: Mon, 27 Nov 2000 08:16:42 +0000 From: Thomas Lockhart Organization: Yes X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15-4mdksmp i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql Cc: pgsql-sql@postgresql.org, tgl@sss.pgh.pa.us Subject: Re: 7.0.3 BUG References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200011/288 X-Sequence-Number: 319 > >> 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