Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 80181475D0F for ; Tue, 12 Nov 2002 00:15:49 -0500 (EST) Received: from crundall.nidweb.net (crundall.nidweb.net [216.229.174.203]) by postgresql.org (Postfix) with ESMTP id 86D32475A3F for ; Tue, 12 Nov 2002 00:15:48 -0500 (EST) Received: from ac6rm.net (localhost [127.0.0.1]) by crundall.nidweb.net (8.12.6/8.12.4) with SMTP id gAC5Fr0C010791 for ; Mon, 11 Nov 2002 21:15:53 -0800 Received: from 24.52.245.104 (SquirrelMail authenticated user martin) by webmail.ac6rm.net with HTTP; Mon, 11 Nov 2002 21:15:53 -0800 (PST) Message-ID: <64726.24.52.245.104.1037078153.squirrel@webmail.ac6rm.net> Date: Mon, 11 Nov 2002 21:15:53 -0800 (PST) Subject: pg_dump / dates: From: "Martin Crundall" To: X-Priority: 3 Importance: Normal Reply-To: pgsql@ac6rm.net X-Mailer: SquirrelMail (version 1.2.9) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/172 X-Sequence-Number: 10314 Question for Tom Lockhart: pg_dump is generating some dates that look like: '2002-09-09 02:11:60.00' or '2002-10-31 23:59:60.00'. psql -f doesn't like these dates. I can sed the :60 to a :59 but -- in the latter case it moves the date backwards a day, which doesn't work for my app. I understand from reading some of the list threads that there's a good reason to allow for "second" field values greater than 59, and per an email thread I had with Tom Lane, this has been addressed -- that it was a rounding error issue on some platforms. I'm running postgres 7.2.2 on slackware 8.1 (kernel 2.4.18). Is there a workaround on this? Tks and kind regards, Martin Crundall