Re: Regression tests fail with tzdata 2024b

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Sven Klemm <sven@timescale.com>

Cc: Wolfgang Walther <walther@technowledgy.de>, pgsql-hackers@lists.postgresql.org

Date: 2024-09-16T15:19:42Z

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

Sven Klemm <sven@timescale.com> writes:
> This is an unfortunate change as this will break extensions tests using
> pg_regress for testing. We run our tests against multiple minor versions
> and this getting backported means our tests will fail with the next minor
> pg release. Is there a workaround available to make the timezone for
> pg_regress configurable without going into every test?

Configurable to what?  If your test cases are dependent on the
historical behavior of PST8PDT, you're out of luck, because that
simply isn't available anymore (or won't be once 2024b reaches
your platform, anyway).

			regards, tom lane