Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ero0n-0007ZI-St for pgsql-admin@arkaria.postgresql.org; Fri, 02 Mar 2018 16:58:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ero0m-00074a-TA for pgsql-admin@arkaria.postgresql.org; Fri, 02 Mar 2018 16:58:24 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ero0m-00074Q-Hi for pgsql-admin@lists.postgresql.org; Fri, 02 Mar 2018 16:58:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ero0j-0006Ii-Sy for pgsql-admin@postgresql.org; Fri, 02 Mar 2018 16:58:23 +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 w22GwJcN030754; Fri, 2 Mar 2018 11:58:19 -0500 From: Tom Lane To: Karl Denninger cc: pgsql-admin@postgresql.org Subject: Re: Time zone issue with 10.3? In-reply-to: <668c10b2-f4dc-7152-6a9e-e70c029e85e0@denninger.net> References: <668c10b2-f4dc-7152-6a9e-e70c029e85e0@denninger.net> Comments: In-reply-to Karl Denninger message dated "Fri, 02 Mar 2018 10:49:17 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <30752.1520009899.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 02 Mar 2018 11:58:19 -0500 Message-ID: <30753.1520009899@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Karl Denninger writes: > I have just tried r0lling forward to 10.3 from 10.1 and suddenly my time > zone declaration blew up. > I was using 'US/Chicago' and was able to get the server to start with > CST6CDT, which is the way the system is set up.  But I'm concerned about > this, because I now get this from trying to query the system tables for > timezone names: > pgsql=# select * from pg_timezone_names; >            name           | abbrev | utc_offset | is_dst > --------------------------+--------+------------+-------- >  Canada/East-Saskatchewan | CST    | -06:00:00  | f > (1 row) > pgsql=# select * from pg_timezone_abbrevs; > ERROR:  time zone "Asia/Yerevan" not recognized > DETAIL:  This time zone name appears in the configuration file for time > zone abbreviation "amst". Hmm, is your build configured with --with-system-tzdata (pg_config --configure would tell you)? If so, is that pointing at a reasonable-looking tree of TZ data? It seems you don't have the TZ data correctly installed in the 10.3 installation, but it's hard to tell who to blame from this much info. Typically the top of the TZ file tree should look like $ ls /usr/share/zoneinfo Africa/ Canada/ GB Indian/ Mexico/ ROK iso3166.tab America/ Chile/ GB-Eire Iran NZ Singapore leapseconds Antarctica/ Cuba GMT Israel NZ-CHAT Turkey posix/ Arctic/ EET GMT+0 Jamaica Navajo UCT posixrules Asia/ EST GMT-0 Japan PRC US/ right/ Atlantic/ EST5EDT GMT0 Kwajalein PST8PDT UTC tzdata.zi Australia/ Egypt Greenwich Libya Pacific/ Universal zone.tab Brazil/ Eire HST MET Poland W-SU zone1970.tab CET Etc/ Hongkong MST Portugal WET CST6CDT Europe/ Iceland MST7MDT ROC Zulu If you're not trying to rely on a platform-provided installation of tzdata, then this ought to be under the share/ subdirectory of the PG installation. regards, tom lane