Re: Updating timezone data to 2018c - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Updating timezone data to 2018c
Date
Msg-id 32159.1516980093@sss.pgh.pa.us
Whole thread Raw
In response to Updating timezone data to 2018c  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Updating timezone data to 2018c
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> I have just bumped into tzdata (https://www.iana.org/time-zones), to
> notice that 2018c has been released. Surely, there will be a refresh for
> the next release?

Yeah, it's on my to-do list for next week.

> At the same time I have played with the instructions in
> src/timezone/README to generate the attached. That's always an
> experience to take. One abbreviation has been visibly removed as far as
> I can see.  I know that Tom does that before each release, I just got
> curious about how this gets updated, and I am wondering if I got the
> thing right ;)

Seems a bit odd, because I see nothing related to West Africa in
the announcement at
http://mm.icann.org/pipermail/tz-announce/2018-January/000048.html

[ pokes around... ] This must be a delayed effect of this change from
2017b:

     Namibia will switch from +01 with DST to +02 all year on
     2017-09-03 at 02:00.  This affects UT offsets starting 2018-04-01
     at 02:00.  (Thanks to Steffen Thorsen.)

Probably, at the time I checked the abbrevs list when I installed 2017b,
WAST was still being detected as a currently-in-use abbreviation.
Now it isn't.  What I'll probably do is mark the abbreviation obsolete
but leave it in place in Africa.txt, since that's what we've generally
done in the past, especially for things that were very recently current.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Invalid result from hash_page_items function
Next
From: Tom Lane
Date:
Subject: Re: Redefining inet_net_ntop