| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Date: | 2019-06-14 18:24:50 |
| Message-ID: | 87ef3w3u8a.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> Anyway, moving on to the question of what should we do about this,
>>> I don't really have anything better to offer than back-patching
>>> 23bd3cec6.
>> The PG12 behavior seems sane, so +1.
Tom> OK, I'll make that happen.
This isn't good enough, because it still picks "UCT" on a system with no
/etc/localtime and no TZ variable. Testing on HEAD as of 3da73d683 (on
FreeBSD, but it'll be the same anywhere else):
% ls -l /etc/*time*
ls: /etc/*time*: No such file or directory
% env -u TZ bin/initdb -D data -E UTF8 --no-locale
[...]
selecting default timezone ... UCT
We need to absolutely prefer UTC over UCT if both match.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-14 19:12:16 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Previous Message | Alvaro Herrera | 2019-06-14 15:37:36 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2019-06-14 18:27:17 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
| Previous Message | Tomas Vondra | 2019-06-14 18:11:35 | Re: [PATCH] Incremental sort (was: PoC: Partial sort) |