Bug #630: date/time storage problem: timestamp parsed incorrectly... - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #630: date/time storage problem: timestamp parsed incorrectly...
Date
Msg-id 20020409013516.49FE447589D@postgresql.org
Whole thread Raw
List pgsql-bugs
Sean Chittenden (sean@chittenden.org) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
date/time storage problem: timestamp parsed incorrectly...

Long Description
It looks like a bad parser or defaults for time values.  The example code below explains the problem best.  I'm not
surewhy, or where... but it took me about a day to track down (PostgreSQL is never wrong!).  If I include a timezone,
thingsseem to work.  For some reason, only dates from yesterday and today break things... I think it's because -7 is
thesame as my timezone, PST (now -7). 

Sample Code
CREATE TABLE timestamp_test (
  utc_timestamp TIMESTAMP NOT NULL
);

INSERT INTO timestamp_tmp VALUES ('2002-4-7 2:0:0.0');
SELECT * from timestamp_tmp;
        utc_date        
------------------------
 2036-06-02 22:55:24-07
(1 row)
INSERT INTO timestamp_tmp VALUES ('2002-4-7 -8 2:0:0.0');
SELECT * from timestamp_tmp;
        utc_date        
------------------------
 2036-06-02 22:55:24-07
 2002-04-07 03:00:00-07
(2 rows)


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: What's the difference?
Next
From: Thomas Lockhart
Date:
Subject: Re: Bug #630: date/time storage problem: timestamp parsed