BUG #12858: Server crash on upgrade due to invalid timezoneset syntax

From: tpoland(at)engineyard(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #12858: Server crash on upgrade due to invalid timezoneset syntax
Date: 2015-03-12 20:08:21
Message-ID: 20150312200821.4031.18195@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 12858
Logged by: Tyler Poland
Email address: tpoland(at)engineyard(dot)com
PostgreSQL version: 9.1.15
Operating system: Gentoo Linux
Description:

Immediately after upgrading from 9.1.9 to 9.1.15 the server (still running
9.1.9) crashes with the error:

2015-03-12 18:39:55.585 UTC,,,13721,,5500d157.3599,9,,2015-03-11 23:35:51
UTC,,0,FATAL,22023,"invalid number for time zone offset in time zone file
""Default"", line 57",,,,,,,,,""

Reviewing the Default timezoneset file reveals that it has changed from:

````

### Before

ART -10800 # Argentina Time
# (America/Argentina/Buenos_Aires)
# (America/Argentina/Cordoba)
# (America/Argentina/Tucuman)
# (America/Argentina/La_Rioja)
# (America/Argentina/San_Juan)
# (America/Argentina/Jujuy)
# (America/Argentina/Catamarca)
# (America/Argentina/Mendoza)
# (America/Argentina/Rio_Gallegos)
# (America/Argentina/Ushuaia)
ARST -7200 D # Argentina Summer Time
````

To
````
ART America/Argentina/Buenos_Aires # Argentina Time
# (America/Argentina/Buenos_Aires)
# (America/Argentina/Cordoba)
# (America/Argentina/Tucuman)
# (America/Argentina/La_Rioja)
# (America/Argentina/San_Juan)
# (America/Argentina/Jujuy)
# (America/Argentina/Catamarca)
# (America/Argentina/Mendoza)
# (America/Argentina/Rio_Gallegos)
# (America/Argentina/Ushuaia)
ARST America/Argentina/Buenos_Aires # Argentina Summer Time
````

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2015-03-12 20:19:30 Re: BUG #12858: Server crash on upgrade due to invalid timezoneset syntax
Previous Message John R Pierce 2015-03-12 19:11:32 Re: BUG #12856: No space left on device, but there is space!