Re: tzdata 2016j

From: Vladimir Borodin <root(at)simply(dot)name>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tzdata 2016j
Date: 2016-12-07 07:03:22
Message-ID: 35404C82-E4B9-4D4C-9653-0CF5B87DDEF1@simply.name
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 6 дек. 2016 г., в 19:19, David Fetter <david(at)fetter(dot)org> написал(а):
>
> On Tue, Dec 06, 2016 at 10:52:47AM -0500, Tom Lane wrote:
>> Vladimir Borodin <root(at)simply(dot)name> writes:
>>> Any chance to get tzdata 2016j in supported branches?
>>
>> When the next scheduled releases come around (February), we'll update
>> to whatever tzdata is current at that time.
>
> I'm guessing that request came through because Vladimir is actually
> affected by the change.
>
> Apparently, you can replace the tzdata file and restart the server per
> https://wiki.postgresql.org/wiki/FAQ#Will_PostgreSQL_handle_recent_daylight_saving_time_changes_in_various_countries.3F <https://wiki.postgresql.org/wiki/FAQ#Will_PostgreSQL_handle_recent_daylight_saving_time_changes_in_various_countries.3F>

Yep, both packages for RHEL and Ubuntu are built with --with-system-tzdata=/usr/share/zoneinfo configure option so updating system package and restarting postgres is sufficient. Thanks!

--
May the force be with you…
https://simply.name

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-12-07 07:05:50 Re: Quorum commit for multiple synchronous replication.
Previous Message Amit Langote 2016-12-07 06:58:03 Re: Partitionning: support for Truncate Table WHERE