From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robins Tharakan <tharakan(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Brazil disables DST - 2019b update |
Date: | 2019-07-12 14:14:14 |
Message-ID: | 27028.1562940854@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robins Tharakan <tharakan(at)gmail(dot)com> writes:
> The 2019b DST update [1] disables DST for Brazil. This would take effect
> starting November 2019. The last DST update in Postgres was 2019a in v11.3
> (since this update came in after the recent-most Postgres release).
Yeah. I intend to install 2019b (or later?) before our next minor
releases.
> Since a ~3 month release cycle may be too close for some users, are there
> any plans for an early 11.5 (or are such occurrences not a candidate for an
> early release)?
We do not consider tzdb updates to be a release-forcing issue.
The fact that we ship tzdb at all is just a courtesy to PG users who
are on platforms that lack a more direct way to get tzdb updates.
The usual recommendation on well-maintained production systems is to
configure PG with --with-system-tzdata, then rely on your platform
vendor for timely updates of that data.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2019-07-12 14:22:58 | Re: Brazil disables DST - 2019b update |
Previous Message | Nikolay Shaplov | 2019-07-12 14:13:43 | Re: [PATCH] get rid of StdRdOptions, use individual binary reloptions representation for each relation kind instead |