Re: New timezones used in regression tests

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christoph Berg <cb(at)df7cb(dot)de>, 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-15 18:42:06
Message-ID: 20140515184206.GE25053@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 12, 2014 at 07:16:48PM -0400, Tom Lane wrote:
> Christoph Berg <cb(at)df7cb(dot)de> writes:
> > 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:
>
> I agree, that seems an entirely gratuitous choice of zone. It does
> seem like a good idea to test a zone that has a nonintegral offset
> from GMT, but we can get that from almost anywhere as long as we're
> testing a pre-1900 date. There's no need to use any zones that aren't
> long-established and unlikely to change.

If we want a nonintegral offset, why are we not using 'Asia/Calcutta',
which is +5:30 from UTC?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-05-15 18:42:21 Re: Freezing without write I/O
Previous Message Bruce Momjian 2014-05-15 18:34:36 Re: Proposal for CSN based snapshots