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-17T05:42:35Z

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:
> On Mon, Sep 16, 2024 at 5:19 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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).

> 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.

			regards, tom lane