From: | "David Wilson" <david(dot)t(dot)wilson(at)gmail(dot)com> |
---|---|
To: | "Jolles, Peter M (GE Infra, Energy)" <peter(dot)jolles(at)ge(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Timestamp shift when importing data |
Date: | 2009-01-03 23:26:45 |
Message-ID: | e7f9235d0901031526p20dc8bf9v4cf8d3668c96aa7a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jan 3, 2009 at 5:59 PM, Jolles, Peter M (GE Infra, Energy)
<peter(dot)jolles(at)ge(dot)com> wrote:
> 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?
Those are the dates of daylight savings time kicking in- which
happens, not coincidentally, at 2am.
What's the type of the field you're trying to import into, and how are
you doing the import?
(Sorry for the duplicate- missed sending to the list the first time.)
--
- David T. Wilson
david(dot)t(dot)wilson(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Schröder | 2009-01-04 09:44:50 | Re: Query planner and foreign key constraints |
Previous Message | Jeremy Harris | 2009-01-03 23:24:05 | Re: Timestamp shift when importing data |