DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=Skdqq7LUvL9qs5e5LVf1vsRbkHcK6ALQkrlAUdIYq2li7WJsZD6MDXypc+18wfUtgY
	2jEq1JdQR7qidnr1xXVexDOtqPpI6Hqj9uRI5cDexkGphDYzEMGe8KUQi2YvB+RgmvLb
	UK4OT2+ReM6U083h4mrfwJip/0Rk6kJVuYOCs=
MIME-Version: 1.0
In-Reply-To: <49B56A7F.6040004@pinpointresearch.com>
References: <eae6a62a0903072358o15b1cefdt661627cefc05b3b0@mail.gmail.com>
	<49B56A7F.6040004@pinpointresearch.com>
Date: Mon, 9 Mar 2009 13:18:33 -0600
Message-ID: <dcc563d10903091218ue6e3f76sbf6a49b2fb8fe06b@mail.gmail.com>
Subject: Re: Urgent PST time changing tonight
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: DM <dm.aeqa@gmail.com>, pgsql-admin@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Mon, Mar 9, 2009 at 1:14 PM, Steve Crawford
<scrawford@pinpointresearch.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.