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 1f1Btb-0003iX-Om for pgsql-admin@arkaria.postgresql.org; Wed, 28 Mar 2018 14:17:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f1Bta-0004l2-K6 for pgsql-admin@arkaria.postgresql.org; Wed, 28 Mar 2018 14:17:46 +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 1f1Bta-0004ks-9O for pgsql-admin@lists.postgresql.org; Wed, 28 Mar 2018 14:17:46 +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 1f1BtX-0006tV-Dw for pgsql-admin@postgresql.org; Wed, 28 Mar 2018 14:17:45 +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 w2SEHVbG019864; Wed, 28 Mar 2018 10:17:31 -0400 From: Tom Lane To: Laurenz Albe cc: Ervin Weber , pgsql-admin Subject: Re: Strange timezone 'math' in 9.6.8 In-reply-to: <1522237846.2820.26.camel@cybertec.at> References: <1522237846.2820.26.camel@cybertec.at> Comments: In-reply-to Laurenz Albe message dated "Wed, 28 Mar 2018 13:50:46 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19862.1522246651.1@sss.pgh.pa.us> Date: Wed, 28 Mar 2018 10:17:31 -0400 Message-ID: <19863.1522246651@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Laurenz Albe writes: > Ervin Weber wrote: >> staging=# select now(), now() at time zone 'fubar+167'; >> [works] >> staging=# select now(), now() at time zone 'fubar+168'; >> ERROR: time zone "fubar+168" not recognized > The cause of the error is the following code in src/timezone/localtime.c, > in function "getsecs": Also note that that isn't our code; it's lock stock and barrel from the IANA tzcode distribution, https://www.iana.org/time-zones So we are (probably) not the only software that will behave like this. regards, tom lane