Re: BUG #16123: DST not respected for America/Sao_Paulo in `timestamp` function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: thushw(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16123: DST not respected for America/Sao_Paulo in `timestamp` function
Date: 2019-11-18 14:41:51
Message-ID: 28436.1574088111@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Mon, Nov 18, 2019 at 6:38 PM PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
>> From Nov 3, America/Sao_Paulo should be offset only 2 hours from UTC due to
>> DTS. I would expect the timestamp to be December 1st midnight.

> I was going to reply with some details about how to find out whether
> you're using timezone data files from PostgreSQL or macOS, and how to
> make sure they're up-to-date in both cases, but now I see that my
> computer (which has up-to-date tzdata) agrees with yours, and
> Wikipedia claims that DST was cancelled this year by presidential
> decree. Why do you think it's wrong?

Indeed, the IANA timezone folks changed their entry in tzdata 2019b,
on the strength of this:

https://mm.icann.org/pipermail/tz/2019-April/027848.html

and other nearby threads in that list archive. 2019b was released
2019-07-02, so any machine with reasonably up-to-date data should
know about this. In the case of Postgres, we absorbed that change
in the August minor releases.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-11-18 14:44:37 BUG #16124: Altering default privileges problem
Previous Message Tomas Vondra 2019-11-18 12:03:12 Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query