Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6Zxm-000TVB-Pg for pgsql-general@arkaria.postgresql.org; Mon, 13 May 2024 17:59:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s6Zwo-003KWE-Ka for pgsql-general@arkaria.postgresql.org; Mon, 13 May 2024 17:58:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6Zwo-003KTj-9F for pgsql-general@lists.postgresql.org; Mon, 13 May 2024 17:58:50 +0000 Received: from wfhigh3-smtp.messagingengine.com ([64.147.123.154]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6Zwl-0002Gl-N7 for pgsql-general@lists.postgresql.org; Mon, 13 May 2024 17:58:49 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.west.internal (Postfix) with ESMTP id A974A180009A; Mon, 13 May 2024 13:58:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Mon, 13 May 2024 13:58:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1715623125; x=1715709525; bh=xK3fU+nbI6h4dIyHWX7D8KlmvZaa23s68cFtHHKqM4E=; b= ICTnccbFTVvTj5Bk1KW8L+Jpfxg0PfhxNx0UwwTij4zg6fI95k3Ic8kjuF20fv4u shcxVmwKfkw+iKLseYnYOleshWHRqoSClY+MVjVTIy7lIBiED61cvjbd0r9Kt29X V6ACQNGicGijU+UhWmPL7v3L6hUghBPqsT8qYt7vW6Mk+OTupWXvw1/48qsDOPGK Mul9T1JGt1llnxnM31sp3jOots5kO/jAfm7xNH8pTRjZAAB8wxWmY9CmAx+wvLQ5 wYJXfXfZsbYMV/s8pcUwFhGciRUJU2smN5rkTYc/b5/ef+6re69iQcKO8vLRBu6J 37PffYhaWz4fl1NG2BwBmA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1715623125; x= 1715709525; bh=xK3fU+nbI6h4dIyHWX7D8KlmvZaa23s68cFtHHKqM4E=; b=U 7rwNRgi6xDItdx/Gmwei0uE8dZUnk8hNc3sZeLIsu3Cgblg8L75l89F5PEq+FucO Vmrd9VQJ1cJ/Fp9o9evOC/5DRqcl3/6E6JM/EjeEYb/JRr6Pa6evZHaO5tmbV2iY Gf4Rx0h20yv5PeKdK2Bzrk3O1GyfkxzyKtk+tzY61obBVuPUmhGLhRGShFztxE9O fzKTJzxa/L+yNv4Dq25hIVNuU8F25FsM92c3JJ+PfF7iiWXuO0ZS7dOubr/HoGZl gHBq5tERdSI1yXD6OyAG/XYntj5MKDGv1d8NqxuPZUrQ6/slreHIeven4OK/BugC FowSURQyWIWZW1nJU6FYg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeggedguddukecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddvjeenucfhrhhomheptegu rhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrd gtohhmqeenucggtffrrghtthgvrhhnpeeuudefjeejgffgtddtgeehgfekueevkeekieet tedtkeffheeivdethfevffegueenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorh hgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggu rhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 13 May 2024 13:58:43 -0400 (EDT) Message-ID: Date: Mon, 13 May 2024 10:58:42 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: UTC is not a time zone? To: Christophe Pettus Cc: "pgsql-generallists.postgresql.org" References: <327870A4-F35C-462C-9F64-E0838374AFDF@thebuild.com> <63e65356-9cb5-48b7-9bc5-5c734013ebe1@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/13/24 10:50 AM, Christophe Pettus wrote: > > >> On May 13, 2024, at 10:48, Adrian Klaver wrote: >> Yes: >> >> https://www.postgresql.org/message-id/5DF49366-10D1-42A4-99BF-F9A7DC3AB0F4%40mailbox.org >> >> Answer: >> >> https://www.postgresql.org/message-id/1273542.1712326418%40sss.pgh.pa.us > > Thanks! Similar, but I don't think it's that. This was a sudden change in a long-running connection that had issued a ton of ` SET TIMEZONE TO 'UTC'; ` before the failure. You sure the timezone file did not get changed under the connection? Why is SET TIMEZONE TO 'UTC being constantly called? -- Adrian Klaver adrian.klaver@aklaver.com