From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
Cc: | DM <dm(dot)aeqa(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Urgent PST time changing tonight |
Date: | 2009-03-09 19:18:33 |
Message-ID: | dcc563d10903091218ue6e3f76sbf6a49b2fb8fe06b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Mar 9, 2009 at 1:14 PM, Steve Crawford
<scrawford(at)pinpointresearch(dot)com> wrote:
> Then there are the scripts that calculate dates externally for feeding into
> your database-backed processes (for fun, try "-d yesterday" and "-d
> tomorrow" in most versions of the "date" command in the vicinity of DST
> changes).
I ran into an issue with this a while back. We were running fairly
modern distros at work, but older ones in production, and a script I'd
written and tested on my workstation failed miserably if you ran it
between midnight and 2/3am the sunday of the time shift on the
production machines.
From | Date | Subject | |
---|---|---|---|
Next Message | DM | 2009-03-10 05:11:37 | Re: Urgent PST time changing tonight |
Previous Message | Steve Crawford | 2009-03-09 19:14:07 | Re: Urgent PST time changing tonight |