Re: tzdata2017a breaks timestamptz regression test
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Date: 2017-03-10T13:53:29Z
Lists: pgsql-hackers
Tom Lane wrote: > For the cases involving the America/Santiago zone, I'm a bit inclined > to just switch that to America/New_York, which seems much less likely > to get fooled with by IANA. But I'm wondering if Alvaro had a specific > reason for using the Santiago zone in those test cases. No, I just used the Santiago zone because it was local. But I agree it's a bad one to use, because in the last decade politicians have been playing with it excessively, so +1 for changing to something else. > What I propose we do about that is replace the America/Caracas test cases > with Europe/Moscow tests, moving the dates as needed to match DST > transitions from when Moscow was observing DST (pre 2011). The comments > in the IANA files indicate that they believe the MSK/MSD abbreviations > have or had real-world usage, so they probably won't replace them with > numeric offsets. We can hope, anyway. Sounds reasonable to me. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix timestamptz regression test to still work with latest IANA zone data.
- f077e1b2e374 10.0 landed
- e573bc3f9a0e 9.4.12 landed
- d8ec6b9c8c26 9.6.3 landed
- c6dc45d157a6 9.3.17 landed
- 92f6e6829a44 9.5.7 landed
- 52f6b2e5a640 9.2.21 landed
-
Don't require dynamic timezone abbreviations to match underlying time zone.
- 39b691f25116 10.0 cited