Re: Timestamp shift when importing data

On Monday 05 January 2009 5:29:19 am Jolles, Peter M (GE Infra, Energy) wrote:
> On Saturday, January 03, 2009 6:27 PM, David T Wilson wrote:
> > 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?
>
> That makes a lot more sense now, although I'm not sure why it is only
> happening in the spring and not in the fall. The original data field is
> a MS Access "General Date". In Postgres it is stored as a timestamp with
> timezone.
>
> To do the import, I tried using an Access append query. I've also tried
> to use the Access export function.
>
> Reading up on Windows XP handling of DST, it appears that it is
> unreliable for pre-2007 time shifts, which would explain why it isn't
> happening with more recent data. Is there any way to ignore DST in an
> import/export transaction?

One way would be to create a field with type "timestamp without timezone" and
import your timestamp data into that field.

>
> Thanks,
> Peter

--
Adrian Klaver
aklaver(at)comcast(dot)net