Updating timezone data to 2018c
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t38089psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 09:18 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t38089_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t38089_1 && git checkout t38089_1Patchset v1 (message #1) is on t38089_1
Hi all,
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?
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 ;)
Thanks,
--
Michael
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
On Fri, Jan 26, 2018 at 10:21:33AM -0500, Tom Lane wrote:
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.
OK. Indeed I can see what you have done in 41fc04f. Thanks for the
update.
--
Michael