From: | Christoph Berg <cb(at)df7cb(dot)de> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: New timezones used in regression tests |
Date: | 2014-05-12 21:51:47 |
Message-ID: | 20140512215147.GB31202@msgid.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: To PostgreSQL Hackers 2014-05-12 <20140512214025(dot)GA31202(at)msgid(dot)df7cb(dot)de>
> 84df54b22e8035addc7108abd9ff6995e8c49264 introduced timestamp
> constructors. In the regression tests, various time zones are tested,
> including America/Metlakatla. Now, if you configure using
> --with-system-tzdata, you'll get an error if that zone isn't there.
> Unfortunately, this is what I'm getting now when trying to build beta1
> on Ubuntu 10.04 (lucid) with tzdata 2010i-1:
>
> SELECT make_timestamptz(1866, 12, 10, 0, 0, 0, 'America/Metlakatla') AT TIME ZONE 'UTC';
> ! ERROR: time zone "America/Metlakatla" not recognized
>
> I can work around it by patching the regression tests, but it would be
> nice if some other zone would be used that wasn't "invented" in 2011.
Fwiw, there is an updated tzdata version in lucid-updates
(2014a-0ubuntu0.10.04), which wasn't used in the pgapt build env until
now, hence the error. Still, the problem will remain on older systems,
and choosing a different time zone for this test seems easy to change.
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-05-12 23:06:01 | Re: Ignore src/tools/msvc/config.pl in code tree for MSVC compilation |
Previous Message | Christoph Berg | 2014-05-12 21:40:25 | New timezones used in regression tests |