Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nBiQ9-0000a0-Tb for pgsql-bugs@arkaria.postgresql.org; Sun, 23 Jan 2022 19:21:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nBiQ8-0006Nf-C3 for pgsql-bugs@arkaria.postgresql.org; Sun, 23 Jan 2022 19:21:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nBiQ8-0006NW-3o for pgsql-bugs@lists.postgresql.org; Sun, 23 Jan 2022 19:21:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nBiQ5-000445-IK for pgsql-bugs@lists.postgresql.org; Sun, 23 Jan 2022 19:20:59 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 20NJKsBg1748522; Sun, 23 Jan 2022 14:20:54 -0500 From: Tom Lane To: kboysreel@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17378: WRONG VALUE ON - A.2. Time Zones In-reply-to: <17378-6747a2c0e12445b5@postgresql.org> References: <17378-6747a2c0e12445b5@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Sun, 23 Jan 2022 02:55:18 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1748520.1642965654.1@sss.pgh.pa.us> Date: Sun, 23 Jan 2022 14:20:54 -0500 Message-ID: <1748521.1642965654@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > I noticed that you have an error on the value for WAT on you documentation > i.e that WAT = UTC -1 instead of UTC +1. > This might be an issue for someone who really doesn't know. > Page - https://www.postgresql.org/docs/7.2/timezones.html PG 7.2 has been out of support since 2007. We keep its docs available for archival purposes, but we're not going to correct errors in them. (FYI, it looks like this behavior was changed in 8.2. It's possible that WAT actually did mean UTC-1 at some point in the past, although it could equally well have been a typo in the hard-wired abbreviations table we used pre-8.2. In any case, that's all ancient history now.) regards, tom lane