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 1htFlh-0006E3-GM for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Aug 2019 18:25:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1htFlg-0001Vv-2G for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Aug 2019 18:25:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1htFlf-0001Vo-Pw for pgsql-hackers@lists.postgresql.org; Thu, 01 Aug 2019 18:25:35 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1htFlZ-0004Cc-Fk for pgsql-hackers@postgresql.org; Thu, 01 Aug 2019 18:25:35 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 4F8CF21D6E; Thu, 1 Aug 2019 14:25:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 01 Aug 2019 14:25:27 -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=fm2; bh=hHkIQMvG6tFBexgTQkHbm88Oy5Z NE1oPmwbHlT2hL4s=; b=bWsK3blTHYqHhTBT+ywH7HbT/AN+dDUPOOX6ZRN3atA AvEj5BTIH6vvjSZc84j5aM50xdDxgWmiunpKz+D2V9KtFnsS5dX3olUYeGhpifyz lgwvX3EfdUpWuMo/qYqyKRvrt5lSr8/MKU/uVJnPsC+z7LbulpHtfQcg2C4b8kN1 rM8B7B5MejPvLI9H61J6cteyKhLSdGdF2BoOok2uLvlcjY/odNVqmofpEY58pJgr TD6xDB6P7qWmjuVXmkaug0FKY1bPFrcHPCQgpXOZzNjL45eSRuOZ52UgfMk9CykI OvyqGrUbHl9dW3+m6i3eaSE+VReENrxMU3QZU7BDJxA== 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=fm3; bh=hHkIQM vG6tFBexgTQkHbm88Oy5ZNE1oPmwbHlT2hL4s=; b=ybmfbZRvoLF60KLyoVG13d QjRIVmi5BoCqYG+JGHsTE+m982Kqu/UzNHWMzr9n1rSYN66jx9adGlIPeQwBMjpq /gkTbJCsogkIVxAWQ/CdyoYnu15fvPT3G9libLt+atr0NsfQPwXOvu8Q7y3bshHW LBhNZ82PVNWu/jfI935vNB8lotXHE/g9TdYeqhY6POgfkxzWfMCh8POO4ZT/Vkfu 2+zZibVqstyOQxVcqA/+cR1n/Vo6a+wuteZUCmmgtTSAi4zKfGx6oa3Vyy/jcA8U cLrlU3/BRUqgtv6Pjhlzn4B4nClo4UreIovC+6ADwb9A8IwA75e9g/saQIaNyHOg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrleejgdduvddvucetufdoteggodetrfdotf 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 4FB978005A; Thu, 1 Aug 2019 14:25:25 -0400 (EDT) Date: Thu, 1 Aug 2019 11:25:23 -0700 From: Andres Freund To: Tom Lane Cc: Shay Rojansky , Thomas Munro , Andrew Gierth , Robert Haas , Stephen Frost , Christoph Berg , PostgreSQL Hackers Subject: Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) Message-ID: <20190801182523.z6onphd2tqkjf2ch@alap3.anarazel.de> References: <8736jwsdv2.fsf@news-spur.riddles.org.uk> <17148.1561568815@sss.pgh.pa.us> <87y31oq9g6.fsf@news-spur.riddles.org.uk> <3961.1564086915@!sss.pgh.pa.us> <5560.1564668481@sss.pgh.pa.us> <20190801171951.pzpp5ywdn4pgqjzc@alap3.anarazel.de> <8331.1564682351@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8331.1564682351@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2019-08-01 13:59:11 -0400, Tom Lane wrote: > Andres Freund writes: > > When used and a symlink, could we resolve the symlink when determining > > the timezone? When loading a timezone in the backend, not during > > initdb. While that'd leave us with the instability, it'd at least would > > help clients etc understand what the setting actually means? > > The question here is what the string "localtime" means when it's in > the timezone variable. Right. > I guess yes, we could install some show_hook for timezone that goes > and looks to see if it can resolve what that means. But that sure > seems to me to be in you've-got-to-be-kidding territory. Fair enough. I'm mildly worried that people will just carry their timezone setting from one version's postgresql.conf to the next as they upgrade. > Especially since the platforms I've seen that do this tend to use hard > links, so that it's questionable whether the pushups would accomplish > anything at all. Hm, debian's is a symlink (or rather a chain of): $ ls -l /usr/share/zoneinfo/localtime lrwxrwxrwx 1 root root 14 Jul 4 14:04 /usr/share/zoneinfo/localtime -> /etc/localtime $ ls -l /etc/localtime lrwxrwxrwx 1 root root 39 Jul 15 15:40 /etc/localtime -> /usr/share/zoneinfo/America/Los_Angeles The system installed versions of postgres I have available all ended up with timezone=localtime. Not sure how long they've been symlinks. I randomly accessed a backup of an older debian installation, from 2014, and there it's a file (with link count 1). But presumably upgrading would yield a postgresql.conf that still had localtime, but localtime becoming a symlink. Greetings, Andres Freund