Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYBks-0006pv-Mr for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Jun 2019 15:53:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hYBkr-0006QF-KP for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Jun 2019 15:53:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYBkp-0006Nt-Np for pgsql-hackers@lists.postgresql.org; Tue, 04 Jun 2019 15:53:41 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYBkm-0003XZ-Lg for pgsql-hackers@postgresql.org; Tue, 04 Jun 2019 15:53:38 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 42FC0447; Tue, 4 Jun 2019 11:53:34 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 04 Jun 2019 11:53:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=ohS7GfLsqg/qfHVmwfhn+4m/JtU rebYHbLywcOLtgx4=; b=bzAs+EbcyCxYOJTUfJSbLHL8HzEcdUyzcP+N/7sfRMy bsbXQc+uU/bl0yXRqBijwSnZ9lRmKYiCIctrvbPzcn/l4hhlVQLzGHwQLjM9mGAO h375NIpRGudN8HBskD+PxIBkTvzkxRpxsks7jx5kdTtG0q9Q4uyTqKrzDb/UA28o GOwCiThsBGurjdGr469Rs2qwGYZRNB2tiFjfl0bmqEpsr5wiO2sdMgsxQqcG7+oM Yu03Bs2Ebj1Pp+YadgNznU4SzZ87Pt8mUWIXptxDXmZ9sESNe9dBVCLA5A9VchFx XkstjzqSytbWADdpKxnymSQNQQ6uvHI5FsPffyr4hUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ohS7Gf Lsqg/qfHVmwfhn+4m/JtUrebYHbLywcOLtgx4=; b=7vP+OHMGH2PyVNgnhyWOGJ 9gfgNYogfVOW3I8ZxqMFhlrchPnWc7rQOm4rZpiokzYm9Jqj7Avgfx1x+xZyIttL cq54JTDzNZIGyvlbuAv9+EpO2w4KjXXiVZHsFKl+lFFWoaEgDzIWBIVzTPnABWgH zHIS62qN5SCpBGqQ3Wac3G00d3XDxpLXLnMGnc0O/HhtLG+BTveeccCfHI3OF2um uYeCQTanfXJiBWbzK1ibF8mZDsZJnrQr+AOZH1NNt9Aj+rnDdZoS+uGUAcLf5a5e Yc43EO8bEhOwohM/+ce+rS1SKalhy0sX2vTCq6o+jDpfAa9lq71syOfHeQNKl7Zw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudefledgleehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucfkphepie ejrdduiedtrddvudekrddvfeejnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgv shesrghnrghrrgiivghlrdguvgenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from intern.anarazel.de (c-67-160-218-237.hsd1.ca.comcast.net [67.160.218.237]) by mail.messagingengine.com (Postfix) with ESMTPA id B9A8E380073; Tue, 4 Jun 2019 11:53:32 -0400 (EDT) Date: Tue, 4 Jun 2019 08:53:30 -0700 From: Andres Freund To: Tom Lane Cc: Christoph Berg , PostgreSQL Hackers Subject: Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) Message-ID: <20190604155330.rtx4qwqzkispsa3x@alap3.anarazel.de> References: <20190604085735.GD24018@msg.df7cb.de> <65800.1559662051@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <65800.1559662051@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2019-06-04 11:27:31 -0400, Tom Lane wrote: > Hm, I don't have a Debian machine at hand, but I'm unable to > reproduce this using macOS or RHEL. I tried things like > > $ TZ=UTC initdb > ... > selecting default timezone ... UTC > ... On debian unstable that's what I get too, both with system and PG tzdata. > BTW, does Debian set up /etc/timezone as a symlink, by any chance, > rather than a copy or hard link? If it's a symlink, we could improve > matters by teaching identify_system_timezone() to inspect it. On my system it's a copy (link count 1, not a symlink). Or did you mean /etc/localtime? Because that's indeed a symlink. If I set the system-wide default, using dpkg-reconfigure -plow tzdata, to UTC I *do* get Etc/UTC. root@alap4:/home/andres/src/postgresql# cat /etc/timezone Etc/UTC root@alap4:/home/andres/src/postgresql# ls -l /etc/timezone -rw-r--r-- 1 root root 8 Jun 4 15:44 /etc/timezone selecting default timezone ... Etc/UTC This is independent of being built with system or non-system tzdata. Enabling debugging shows: selecting default timezone ... symbolic link "/etc/localtime" contains "/usr/share/zoneinfo/Etc/UCT" TZ "Etc/UCT" gets max score 5200 Etc/UCT Greetings, Andres Freund