| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-28 20:30:28 | Re: BUG #1790: coredump in postgres |
| Previous Message | Richard Huxton | 2005-07-28 15:01:20 | Re: BUG #1795: mirroring |