Received: from localhost (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 78A36634F20
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sun,  8 Mar 2009 05:30:53 -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 00243-07 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sun,  8 Mar 2009 05:30:47 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from wf-out-1314.google.com (wf-out-1314.google.com
 [209.85.200.168])
	by mail.postgresql.org (Postfix) with ESMTP id E04C6634D3D
	for <pgsql-admin@postgresql.org>; Sun,  8 Mar 2009 05:30:45 -0300 (ADT)
Received: by wf-out-1314.google.com with SMTP id 23so1253985wfg.28
	for <pgsql-admin@postgresql.org>; Sun, 08 Mar 2009 00:30:43 -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;
	bh=b+vJ/jiQ5L9DcUmWBVCgSh1cs2SZiqFcY/l7Uw7yFlM=;
	b=jAhLnrJn+UaUPEEY8B4MNlTzrlRjqcVFwO13FDHLTOkArN9NF3yH0ucK8rJOEj5mjl
	6NUXdaMI5twydAHoiSsx9oC9AsuL0rbW8pc9nf3sk/3v0Xyo/VORgvWmM44Vnoul+b+1
	rfLyjXRe+l3jhy2rY5CdB1IDoV38w2ZidQc8U=
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;
	b=mhhm6Yc7tpSphwfogW+Ks3gzemWYCBydkGuRlfrMfEA/tjdbeUQVGjVLmW93nPxFr3
	Olf2GKC+cfnmnJ1m/OVjujIe1ZSyF4koYDeTxWDqUkxxWrNpwxad9O82dv5+Cp1wPIWl
	da1XnriGmuaS6+bnZ8NYPwo3cmAsluVwGkaHY=
MIME-Version: 1.0
Received: by 10.142.154.9 with SMTP id b9mr1362519wfe.126.1236501043596; Sun,
	08 Mar 2009 00:30:43 -0800 (PST)
In-Reply-To: <dcc563d10903080023p73709f12lf64796ff81908d34@mail.gmail.com>
References: <eae6a62a0903072358o15b1cefdt661627cefc05b3b0@mail.gmail.com>
	<dcc563d10903080023p73709f12lf64796ff81908d34@mail.gmail.com>
Date: Sun, 8 Mar 2009 00:30:43 -0800
Message-ID: <eae6a62a0903080030g62f3122ax3d768518f9700600@mail.gmail.com>
Subject: Re: Urgent PST time changing tonight
From: DM <dm.aeqa@gmail.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Content-Type: multipart/alternative; boundary=000e0cd331de77cf12046497553e
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5
	tests=HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200903/109
X-Sequence-Number: 31609

--000e0cd331de77cf12046497553e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Thanks Scott for the quick response, do I need to do anything at my end to
solve this issue.

People access our servers from Pacific, Central, Mountain and East Time
zones.

Please let me know if i have to do any settings/configuration changes to the
configuration files.

thanks
Deepak Murthy
On Sun, Mar 8, 2009 at 12:23 AM, Scott Marlowe <scott.marlowe@gmail.com>wrote:

> On Sun, Mar 8, 2009 at 12:58 AM, DM <dm.aeqa@gmail.com> wrote:
> > Hi All,
> > PST time changing tonight, I am not sure if this is going to affect the
> > database.
> > Please throw some light if the time change affect on our production
> system.
> > Briefly - We have 2 production database servers with postgresql 8.3.3 and
> > pgpool 2.1 version running.
>
> pg includes its own tz data files, so running 8.3.3 might be some
> issue if you handle odd timezones, but generally the dst offset change
> is no big deal.  all the timestamps are stored internally in gmt.
>

--000e0cd331de77cf12046497553e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Thanks Scott for the quick response, do I need to do anything at my en=
d to solve this issue.<br></div><div><br></div><div>People access our serve=
rs from Pacific, Central, Mountain and East Time zones.</div><div><br></div=
>
<div>Please let me know if i have to do any settings/configuration changes =
to the configuration files.</div><div><br></div><div>thanks</div><div>Deepa=
k Murthy<br><div class=3D"gmail_quote">On Sun, Mar 8, 2009 at 12:23 AM, Sco=
tt Marlowe <span dir=3D"ltr">&lt;<a href=3D"mailto:scott.marlowe@gmail.com"=
>scott.marlowe@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im">On Sun, Mar 8, 2009 at 12=
:58 AM, DM &lt;<a href=3D"mailto:dm.aeqa@gmail.com">dm.aeqa@gmail.com</a>&g=
t; wrote:<br>

&gt; Hi All,<br>
&gt; PST time changing tonight, I am not sure if this is going to affect th=
e<br>
&gt; database.<br>
&gt; Please throw some light if the time change affect on our production sy=
stem.<br>
&gt; Briefly - We have 2 production database servers with postgresql 8.3.3 =
and<br>
&gt; pgpool 2.1 version running.<br>
<br>
</div>pg includes its own tz data files, so running 8.3.3 might be some<br>
issue if you handle odd timezones, but generally the dst offset change<br>
is no big deal. =A0all the timestamps are stored internally in gmt.<br>
</blockquote></div><br></div>

--000e0cd331de77cf12046497553e--