Regression tests fail with tzdata 2024b

Wolfgang Walther <walther@technowledgy.de>

From: Wolfgang Walther <walther@technowledgy.de>

To: pgsql-hackers@lists.postgresql.org

Date: 2024-09-14T13:02:38Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Run regression tests with timezone America/Los_Angeles.
- b28b9b19bbe3 13.17 landed
- b27622c90869 14.14 landed
- 2b94ee58bf25 15.9 landed
- 2abc88958039 16.5 landed
- 205813da4c26 12.21 landed
- b8ea0f675f35 18.0 landed
- 6283ff2018e3 17.0 landed
Don't require bleeding-edge timezone data in timestamptz regression test.
- 8d7af8fbe734 9.5.0 cited

Attachments

regression.diffs (text/plain)
v1-0001-Run-regression-tests-with-timezone-America-Los_An.patch (text/x-patch) patch v1-0001

Building --with-system-tzdata and the latest tzdata 2024b fails the 
regression tests for me (see attached .diffs). This seems to be because 
of [1], which changed the way "PST8PDT" is handled. This is the timezone 
that the regression tests are run with.

 From 2024b on, "PST8PDT" is the same as "America/Los_Angeles", so by 
changing the regression tests to use the latter as the default, we're 
getting consistent output on at least 2024a and 2024b.

Patch attached.

Best,

Wolfgang

[1]: 
https://github.com/eggert/tz/commit/a0b09c0230089252acf2eb0f1ba922e99f7f4a03