Re: Tom Lane 2019-06-11 <24452.1560285...@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? > So I'm still mystified by Christoph's report, and am forced to suspect > pilot error -- specifically, /etc/localtime not containing what he said. On Debian unstable, deleting /etc/timezone, $TZ not set, and with this symlink: lrwxrwxrwx 1 root root 27 Mär 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 = 'UCT' timezone = 'UCT' /usr/lib/postgresql/12/bin/initdb -D pgdata $ grep timezone pgdata/postgresql.conf log_timezone = 'Etc/UTC' timezone = 'Etc/UTC' Same behavior on Debian Stretch (stable): lrwxrwxrwx 1 root root 27 Mai 7 11:14 /etc/localtime -> /usr/share/zoneinfo/Etc/UTC $ grep timezone pgdata/postgresql.conf log_timezone = 'UCT' timezone = 'UCT' $ grep timezone pgdata/postgresql.conf log_timezone = 'Etc/UTC' timezone = 'Etc/UTC' > 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. Christoph
