Also, setting my timezone to "Melbourne, Australia" results in it still being GMT+10 with a really weird timezone abbreviation:
This was a pre-existing issue, but the
timezone names for Australia really need an overhaul (they do not appear in order and there are some non-standard names and duplicates, as well as at least one timezone that doesn't even exist!). For example, I use the standard timezone names in PostgreSQL at my workplace:
- Australia/Melbourne - this is suitable for the state of Victoria and automatically accommodates daylight savings (AEST vs AEDT); by the way, the timezone "Australian Eastern Summer Standard Time" is not a real timezone name - we use "Australian Eastern Daylight Time" (AEDT) instead
- Australia/Sydney - suitable for the state of New South Wales and the ACT; typically this is the same as Australia/Melbourne
- Australia/Hobart - suitable for the state of Tasmania; typically this is the same as Australia/Melbourne
- Australia/Adelaide - suitable for the state of South Australia (as well as the city of Broken Hill, NSW) and accommodates daylight savings (ACST vs ACDT)
- Australia/Brisbane - suitable for the state of Queensland, as they do not observe daylight savings
- Australia/Darwin - suitable for the Northern Territory (they do not observe daylight savings either)
- Australia/Perth - suitable for the state of Western Australia (again, no daylight savings)
I'm not sure if the database system you're using automatically accommodates daylight savings, but if not, perhaps at least the timezones could be updated to reflect those on the
Australia government website.
It would be great if you're able to do something with this when you get a chance.