From: | "Robert M(dot) Meyer" <rmeyer(at)installs(dot)com> |
---|---|
To: | Jeff Boes <jboes(at)nexcerpt(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Odd error in timestamp processing |
Date: | 2002-07-23 18:40:59 |
Message-ID: | 1027449659.25568.37.camel@skymaster |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
We had this problem, too. Very annoying. It appears to be a bug in
7.1.x. The way we got around it was to dump the DB out to a file and
run sed on the file with the script:
s/:60/:59/
Then feeding that output into psql.
Of course, our database doesn't use ':' followed by numbers for anything
but timestamps so your mileage may vary.
Hope this helps...
Cheers!
Bob
On Tue, 2002-07-23 at 14:14, Jeff Boes wrote:
> Recently we transferred our database from a 7.1 system to a 7.2 using:
>
> $ pg_dump -h old_host | psql
>
> During this, we saw this message:
>
>
> ERROR: copy: line 15926, Bad timestamp external representation
> '2002-07-21 06:54:60.00-04'
>
> (It's the '60 seconds' part of the timestamp that is causing the problem,
> I'm sure.) How might this have happened? Some kind of rounding error?
>
> --
> Jeff Boes vox 616.226.9550 ext 24
> Database Engineer fax 616.349.9076
> Nexcerpt, Inc. http://www.nexcerpt.com
> ...Nexcerpt... Extend your Expertise
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
--
Robert M. Meyer
Sr. Network Administrator
DigiVision Satellite Services
14 Lafayette Sq, Ste 410
Buffalo, NY 14203-1904
(716)332-1451
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Boes | 2002-07-23 18:52:01 | Re: Recurring 'FATAL 1' error in postmaster log |
Previous Message | Robert M. Meyer | 2002-07-23 18:29:52 | Re: Postgres performance slowly gets worse over a month |