Re: Regression tests fail with tzdata 2024b
Wolfgang Walther <walther@technowledgy.de>
From: Wolfgang Walther <walther@technowledgy.de>
To: Tom Lane <tgl@sss.pgh.pa.us>, Sven Klemm <sven@timescale.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-09-17T06:39:53Z
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
Tom Lane: >> I was wondering whether the timezone used by pg_regress could be made >> configurable. > > Yes, I understood that you were suggesting that. My point is that > it wouldn't do you any good: you will still have to change any > regression test cases that depend on behavior PST8PDT has/had that > is different from America/Los_Angeles. That being the case, > I don't see much value in making it configurable. Just changing it back to PST8PDT wouldn't really help as Tom pointed out. You'd still get different results depending on which tzdata version you are running with. The core regression tests need to be run with a timezone that tests special cases in the timezone handling code. But that might not be true for extensions - all they want could be a stable output across major and minor versions of postgres and versions of tzdata. It could be helpful to set pg_regress' timezone to UTC, for example? Best, Wolfgang