Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id CF0E1634D3D for ; Sun, 8 Mar 2009 05:18:15 -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 96904-07 for ; Sun, 8 Mar 2009 05:18:11 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mail.postgresql.org (Postfix) with ESMTP id 59BAC634FBD for ; Sun, 8 Mar 2009 04:58:47 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id f6so1263119rvb.43 for ; Sat, 07 Mar 2009 23:58:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=68Uq4VFcT0w9AOiqd3Nj14vMkaocMBHxNjymeEZyc9U=; b=EZ3hQ2FIMzZLIDlvhXDYenT4kWom2+PPZolJYKHptf0eQLOcKkV+E1PoWD9sW1pWax LXNctz7MCJYpIxd/pq8CjtaupcI8iqL7yXQ6RaQbJPCkwl7TuCkooeyNO7TmcrykvfGv Hb6sdBQPXMvJRdHZL/56WEJ7nVWBlzvCCeLVE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dFgqDu9+uaXYeXR5WIyWS9hHjm+2jHaWeDUZM7d1lMKE+WwxTEgo9l+kUlqV+mVOua Bz/elePXnzY8Yks4Crz39ArThHY8gzT4Pq2FLd0RaY021udO45ZfFxWphDg0Oi2qqL6c AHbcldP+/HCUizEon08Uq5aeYB8k8ClpibVD8= MIME-Version: 1.0 Received: by 10.143.156.17 with SMTP id i17mr1946550wfo.13.1236499126018; Sat, 07 Mar 2009 23:58:46 -0800 (PST) Date: Sat, 7 Mar 2009 23:58:45 -0800 Message-ID: Subject: Urgent PST time changing tonight From: DM To: pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary=001636e1fca22be41a046496e3ff 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/107 X-Sequence-Number: 31607 --001636e1fca22be41a046496e3ff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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. Here is the configuration details about time zone. #log_timezone = unknown # actually, defaults to TZ environment setting datestyle = 'iso, mdy' #timezone = unknown # actually, defaults to TZ environment # setting #timezone_abbreviations = 'Default' # Select the set of available time zone # abbreviations. Currently, there are # Default # Australia # India # You can create your own file in # share/timezonesets/. log_timezone, timezone and timezone_abbreviations are set to default. Thanks Deepak Murthy --001636e1fca22be41a046496e3ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All,

PST time changing tonight, I am not s= ure if this is going to affect the database.=A0
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.

Here is the config= uration details about time zone.

#log_timezone =3D= unknown = # actually, defaults to TZ environment setting
datestyle =3D 'iso, mdy'
#timezone =3D unknown # actually, de= faults to TZ environment
# setting
#timezone_abbreviations =3D 'Default' =A0 =A0 # Select the set= of available time zone
# abbreviations. =A0Currently, there are
<= div> # = =A0 Default
#= =A0 Australia
# =A0 India
# You can create your own file in
#= share/timezonesets/.

log_timezone, timezone and t= imezone_abbreviations are set to default.

Thanks
Deepak Murthy
--001636e1fca22be41a046496e3ff--