Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 44895633670 for ; Sun, 8 Mar 2009 06:29:12 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 12243-06 for ; Sun, 8 Mar 2009 06:29:06 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f176.google.com (mail-gx0-f176.google.com [209.85.217.176]) by mail.postgresql.org (Postfix) with ESMTP id A9CE56324D1 for ; Sun, 8 Mar 2009 06:29:09 -0300 (ADT) Received: by gxk24 with SMTP id 24so2421699gxk.19 for ; Sun, 08 Mar 2009 01:29:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DISUkAff82zAwT8WXQ4TTsUAlr7PLAIUdjvtIHJNKLc=; b=C1jURcnP7KyPSMMQBhOog00f2F47bLr3M6tQLpqiXX91A6A07ar51bfBZl9T7RGp2Q BnjYbkFNZrkbxIzvf+3dRYGuP78YDp5HTiFZX1w1Iq4tiR2yLWZu5h+EBaZndrKkvHaB zMJN3NAaF9MWDU1OG3MpovLBbSxSFOhrY+OIs= 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=r5VcEFBOMt/Uh7O8iU0rx440X0JsrMsoVAejR7isAks8le6M8RORxsi9rrCmAIIMtk 7o5SUsl9Z6S4lwnciyC2qcoPi033jphjuas1x+VOJ0ot7KSEEgaY1XBmml+Dj+iIQdx+ s/tcrCN6k/mCufwM6h+1YHqhDuNfFNsC0NH/k= MIME-Version: 1.0 Received: by 10.151.145.21 with SMTP id x21mr8287808ybn.213.1236504548141; Sun, 08 Mar 2009 01:29:08 -0800 (PST) In-Reply-To: References: Date: Sun, 8 Mar 2009 02:29:08 -0700 Message-ID: Subject: Re: Urgent PST time changing tonight From: Scott Marlowe To: DM Cc: pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/112 X-Sequence-Number: 31612 On Sun, Mar 8, 2009 at 1:53 AM, DM wrote: > Thanks Scott, > If i leave the system as is without any upgrade, what issues i might see any > idea? > do postgres has any patches for the changes. i dont want to install a new > databae at this time, i have 1 hr to go.. > Thanks Assuming that some update to DST got missed, then you're output will all be off by an hour from what they should be when retrieved for that timezone that has it wrong. I remember there being something a while back about moving one of the timezones a few days. You can always create and retrieve timestamps ahead of time (i.e. a timestamp in the future) and see what offset it has to see if it's coming out right. The real problem gets created when timestamps are inserted now for the future. If there's a rule that we fall back 1 week off from what your TZ data says, and you insert it today, with the old TZ on your machine, it will be inserted as the wrong time, with the wrong offset to get it to GMT. This cropped up a year ago with some change our windows machines at work didn't have, and all the schedules created by those machines were off by an hour until the newly created events (created with the right timezone offset values) started showing up and we got past the window where time actually did match up again. So, leaving these to stew can be a real problem, if you're not keeping up with the tz info.