| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Richard Troy <rtroy(at)ScienceTools(dot)com> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org>, pgsql-announce(at)postgresql(dot)org |
| Subject: | Re: Production systems beware: U.S. Daylight Savings Time comes at a new time this year |
| Date: | 2007-02-01 21:08:14 |
| Message-ID: | 1170364093.5451.40.camel@state.g2switchworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2007-02-01 at 15:15, Richard Troy wrote:
> Hello All,
>
> it was recently brought to my attention that last year the U.S. altered
> the dates when Daylight Savings Time starts and ends. Many if not most
> computers presume the old change dates and therefore, if left to change
> automatically, will change at the wrong times. This will be vital for
> people in the database community who manage applications that need
> accurate timestamps.
>
> You can read up on this issue here, among other places:
>
> http://www.washingtonpost.com/wp-dyn/content/article/2007/01/31/AR2007013102318.html?referrer=emailarticle
>
> I've never investigated how NTP servers handle DST changes - that is,
> whether they switch with the fabrication that we have more daylight hours
> or leave it to clients. Hmmm... Anybody know? It'd be nice to know that
> we can trust our NTP servers to tell our systems what time it is and
> therefore ignore this issue for those systems that are NTP clients.
As far as I know, NTP servers run on UTC, so time zone changes are
outside the realm of things they worry about.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-01 21:12:06 | Re: Production systems beware: U.S. Daylight Savings Time comes at a new time this year |
| Previous Message | korryd | 2007-02-01 21:06:47 | Re: How to allow users to log on only from my application |