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 1pU7jn-0000k4-Uv for pgsql-bugs@arkaria.postgresql.org; Mon, 20 Feb 2023 15:05:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pU7jm-0006yi-Nt for pgsql-bugs@arkaria.postgresql.org; Mon, 20 Feb 2023 15:05:54 +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 1pU7jm-0006yZ-FO for pgsql-bugs@lists.postgresql.org; Mon, 20 Feb 2023 15:05:54 +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 1pU7jk-0003tj-2R for pgsql-bugs@lists.postgresql.org; Mon, 20 Feb 2023 15:05:54 +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 31KF5npq3566455; Mon, 20 Feb 2023 10:05:49 -0500 From: Tom Lane To: =?UTF-8?Q?Umut_TEK=C4=B0N?= cc: david.g.johnston@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: Inconsistent 'at time zone' conversion In-reply-to: References: <3449861.1676850587@sss.pgh.pa.us> Comments: In-reply-to =?UTF-8?Q?Umut_TEK=C4=B0N?= message dated "Mon, 20 Feb 2023 13:54:15 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3566453.1676905549.1@sss.pgh.pa.us> Date: Mon, 20 Feb 2023 10:05:49 -0500 Message-ID: <3566454.1676905549@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =?UTF-8?Q?Umut_TEK=C4=B0N?= writes: > So, it should be related to the date. Yet, as you can see '2004-10-19 > 10:23:54+03' is nearly the same time of the year 18 years and 4 months ago. > So, the same DST rules should apply, but it does not. It's folly to make such an assertion without having checked tzdb ;-). DST laws change from time to time. A bit of experimentation shows that Postgres does think both those zones were observing DST on 2004-10-19, and I would be quite surprised if it's wrong about that. (Even if it's wrong, that would be tzdb's bug not ours.) regards, tom lane