Hi Tom,<br /><br />While setting timezone using SET command (say GMT+3:30), postgres sometimes crashes randomly. <br
/>Afterdebugging into the code, it is observed that if tzload() call fails in pg_tzset() for whatever reason, the
returnedvalue of the function then have garbage values for state variable. And this will assigned to session_timezone
inassign_timezone() function later.<br /><br />Now as session_timezone.state variable has garbage values, it is causing
aserver crash further. Unfortunately it is happening with few garbage values and not crashing the server always.<br
/><br/>Here are the two statements used:<br /><br />SET TimeZone = 'GMT+3:30';<br />SELECT '1969-12-31
20:30:00'::timestamptz;<br/><br />After, initializing tzstate variable to zero in pg_tzset() function, server crash
didn'tcome up again.<br /><br />The upstream zoneinfo project just released a new tzcode version, 2010c. After syncing
thecode to this version does not lead to server crash. The new release is now initializing the tzstate variable with
zerosto avoid any garbage values.<br /><br />PFA, patch which will bring us up-to date to 2010c.<br /><br />Note: This
behaviorwas observed on Windows machine.<br /><br />Thanks<br clear="all" /><br />-- <br />Jeevan B Chalke<br
/>SoftwareEngineer, R&D<br />EnterpriseDB Corporation<br /> The Enterprise Postgres Company<br /><br />Phone: +91
2030589500<br /><br />Website: <a href="http://www.enterprisedb.com">www.enterprisedb.com</a><br />EnterpriseDB Blog:
<ahref="http://blogs.enterprisedb.com/">http://blogs.enterprisedb.com/</a><br /> Follow us on Twitter: <a
href="http://www.twitter.com/enterprisedb">http://www.twitter.com/enterprisedb</a><br/><br />This e-mail message (and
anyattachment) is intended for the use of the individual or entity to whom it is addressed. This message contains
informationfrom EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under
applicablelaw. If you are not the intended recipient or authorized to receive this for the intended recipient, any use,
dissemination,distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have
receivedthis e-mail in error, please notify the sender immediately by reply e-mail and delete this message.<br />
