Strange results of CURRENT_TIMESTAMP

From: Marek PUBLICEWICZ <M(dot)Publicewicz(at)elka(dot)pw(dot)edu(dot)pl>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Strange results of CURRENT_TIMESTAMP
Date: 2001-03-21 17:35:03
Message-ID: Pine.SOL.4.30.0103211824460.5726-100000@elektron.elka.pw.edu.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

During repopulation of the database (using the results of the pg_dump
program), I spot two strange things:

- fields defined as TIMESTAMP DEFAULT CURRENT_TIMESTAMP sometimes generate
invalid format of the date, for instance:

2001-02-10 13:11:60.00+01 - which follows the records
2001-02-10 13:10:59.00+01

Which means, that the proper timestamp should look like:
2001-02-10 13:11:00.00+01

- I have a float4 field, which contains the value 3e-40 (approximately).
I know it's there - the queries return it without any problem. Problem
occurs again when I try to repopulate the table. Having such a value
in a line generated by pg_dump (in form of COPY from stdin) I get
the error:

Bad float4 input format -- underflow.

When I redefine the field as a float8 everything works fine. But why
does it occur during repopulation - when in fact such a value did exist
in the table before the table was drop.

I'am running Postgresql 7.0.2

thanks for help

Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2001-03-21 17:45:25 RELEASE STOPPER? nonportable int64 constants in pg_crc.c
Previous Message Mikheev, Vadim 2001-03-21 17:18:08 RE: Beta 6 Regression results on Redat 7.0.