| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Date: | 2019-06-04 08:57:35 |
| Message-ID: | 20190604085735.GD24018@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Re: Tom Lane 2019-04-26 <E1hK8qL-0005yH-VX(at)gemulon(dot)postgresql(dot)org>
> Update time zone data files to tzdata release 2019a.
>
> DST law changes in Palestine and Metlakatla.
> Historical corrections for Israel.
>
> Etc/UCT is now a backward-compatibility link to Etc/UTC, instead
> of being a separate zone that generates the abbreviation "UCT",
> which nowadays is typically a typo. Postgres will still accept
> "UCT" as an input zone name, but it won't output it.
There is something wrong here. On Debian Buster/unstable, using
system tzdata (2019a-1), if /etc/timezone is "Etc/UTC":
11.3's initdb adds timezone = 'UCT' to postgresql.conf
12beta1's initdb add timezone = 'Etc/UCT' to postgresql.conf
Is that expected behavior? Docker users are complaining that "UCT"
messes up their testsuites. https://github.com/docker-library/postgres/issues/577
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-06-04 10:20:14 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Previous Message | Peter Eisentraut | 2019-06-04 07:34:54 | pgsql: Add command column to pg_stat_progress_create_index |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-06-04 10:20:14 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Previous Message | Konstantin Knizhnik | 2019-06-04 08:43:55 | Re: Pinned files at Windows |