Re: Bad timestamp external representation - Mailing list pgsql-general

From Joseph Shraibman
Subject Re: Bad timestamp external representation
Date
Msg-id 3B5DD30C.82E0E9CC@selectacast.net
Whole thread Raw
In response to Bad timestamp external representation  ("tamsin" <tg_mail@bryncadfan.co.uk>)
List pgsql-general
It's a bug in timestamp output.

# select '2001-07-24 15:55:59.999'::timestamp;
         ?column?
---------------------------
 2001-07-24 15:55:60.00-04
(1 row)

Richard Huxton wrote:
>
> From: "tamsin" <tg_mail@bryncadfan.co.uk>
>
> > Hi,
> >
> > Just created a db from a pg_dump file and got this error:
> >
> > ERROR:  copy: line 602, Bad timestamp external representation '2000-10-03
> > 09:01:60.00+00'
> >
> > I guess its a bad representation because 09:01:60.00+00 is actually 09:02,
> > but how could it have got into my database/can I do anything about it?
> The
> > value must have been inserted by my app via JDBC, I can't insert that
> value
> > directly via psql.
>
> Seem to remember a bug in either pg_dump or timestamp rendering causing
> rounding-up problems like this. If no-one else comes up with a definitive
> answer, check the list archives. If you're not running the latest release,
> check the change-log.
>
> HTH
>
> - Richard Huxton
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly

--
Joseph Shraibman
jks@selectacast.net
Increase signal to noise ratio.  http://www.targabot.com

pgsql-general by date:

Previous
From: missive@frontiernet.net (Lee Harr)
Date:
Subject: Re: pqReadData() -- backend closed the channel unexpectedly.
Next
From: Mike Finn
Date:
Subject: Re: Referential cascade technique