From: | "Jolles, Peter M (GE Infra, Energy)" <peter(dot)jolles(at)ge(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Timestamp shift when importing data |
Date: | 2009-01-03 22:59:57 |
Message-ID: | 450587DECE7D17438DC4C9EFD12F0A430AAAD7DB@ALPMLVEM08.e2k.ad.ge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am trying to migrate several years of historical data with timestamps
from an MS Access database to Postgres. I am running into an issue where
specific dates/times get pushed one hour ahead, which creates duplicate
date/time stamps or failes the import if I have that defined as my
primary key. The time that gets shifted is always 2:00 AM to 2:55 AM
(data is in 5 minute blocks). What I don't understand is that it only
seems to happen on the following dates (m/d/yy format):
4/7/02
4/6/03
4/4/04
4/3/05
4/2/06
For example, on these days, 4/7/02 2:00 AM imports to 4/7/02 3:00 AM.
4/6/03 2:15 AM imports as 4/6/03 3:15 AM, etc. All other dates and times
do not give any errors. I have tried to extract the date and create a
text field in MS Access, I get the same error when imported to Postgres.
Is there some significance to these dates?
Thanks,
Peter Jolles
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Harris | 2009-01-03 23:24:05 | Re: Timestamp shift when importing data |
Previous Message | Tino Wildenhain | 2009-01-03 22:52:33 | Re: auto insert data every one minute |