Skip site navigation (1) Skip section navigation (2)

Re: Insert statement changes timestamp value from MS Access

From: Richard Huxton <dev(at)archonet(dot)com>
To: David Dabney <David(dot)Dabney(at)noaa(dot)gov>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Insert statement changes timestamp value from MS Access
Date: 2005-07-28 15:02:41
Message-ID: 42E8F391.1060702@archonet.com (view raw or flat)
Thread:
Lists: pgsql-bugs
David Dabney wrote:
> The more I thought about this I realized it's not a bug and I'm sorry to 
> have perstered the list.  The fact that the data logger was deployed 
> before and after a time change and it was not setup to update itself 
> created this problem.  I just have to push forward all the times after 
> the change and then import the data.  We've been trying to get the 
> scientists to use UTC.....maybe this will help them understand why they 
> should be doing that.

The other thing you should do is use "timestamp with time zone" to store 
your timestamps. Otherwise, you aren't storing an absolute time at all.

-- 
   Richard Huxton
   Archonet Ltd

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-07-28 20:30:28
Subject: Re: BUG #1790: coredump in postgres
Previous:From: Richard HuxtonDate: 2005-07-28 15:01:20
Subject: Re: BUG #1795: mirroring

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group