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 1hblzM-0001c5-42 for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Jun 2019 13:11:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hblzJ-0005vC-Eo for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Jun 2019 13:11:25 +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 1hblzJ-0005v5-6I for pgsql-hackers@lists.postgresql.org; Fri, 14 Jun 2019 13:11:25 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hblzG-0000Li-QC for pgsql-hackers@postgresql.org; Fri, 14 Jun 2019 13:11:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x5EDBFfN026949; Fri, 14 Jun 2019 09:11:15 -0400 From: Tom Lane To: Christoph Berg cc: PostgreSQL Hackers Subject: Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) In-reply-to: <20190614095546.GA15107@msg.df7cb.de> References: <20190604085735.GD24018@msg.df7cb.de> <65800.1559662051@sss.pgh.pa.us> <20190605084735.GC15829@msg.df7cb.de> <24452.1560285699@sss.pgh.pa.us> <20190614095546.GA15107@msg.df7cb.de> Comments: In-reply-to Christoph Berg message dated "Fri, 14 Jun 2019 11:55:46 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <26947.1560517875.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 14 Jun 2019 09:11:15 -0400 Message-ID: <26948.1560517875@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Christoph Berg writes: > Re: Tom Lane 2019-06-11 <24452.1560285699@sss.pgh.pa.us> >> The only way I can get it to pick "Etc/UCT" is if that's what I put >> into /etc/localtime. (In which case I maintain that that's not a bug, >> or at least not our bug.) > Did you try a symlink or a plain file for /etc/localtime? Symlink --- if it's a plain file, our code can't learn anything from it. > On Debian unstable, deleting /etc/timezone, $TZ not set, and with this s= ymlink: > lrwxrwxrwx 1 root root 27 M=C3=A4r 28 14:49 /etc/localtime -> /usr/share= /zoneinfo/Etc/UTC > /usr/lib/postgresql/11/bin/initdb -D pgdata > $ grep timezone pgdata/postgresql.conf > log_timezone =3D 'UCT' > timezone =3D 'UCT' > /usr/lib/postgresql/12/bin/initdb -D pgdata > $ grep timezone pgdata/postgresql.conf > log_timezone =3D 'Etc/UTC' > timezone =3D 'Etc/UTC' That's what I'd expect. Do you think your upthread report of HEAD picking "Etc/UCT" was a typo? Or maybe you actually had /etc/localtime set that way? >> 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 23bd3ce= c6. > The PG12 behavior seems sane, so +1. OK, I'll make that happen. regards, tom lane