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.98.2) (envelope-from ) id 1xTk6y-00000000WHi-11fK for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Nov 2026 18:10:24 +0000 Received: from localhost ([127.0.0.1]:41130 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xTk6x-0000000D2Yo-2dfG for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Nov 2026 18:10:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:38960) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xTk6x-0000000D2Ye-1YOy for pgsql-bugs@lists.postgresql.org; Wed, 18 Nov 2026 18:10:23 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xTk6u-00000000MHF-0gka for pgsql-bugs@lists.postgresql.org; Wed, 18 Nov 2026 18:10:22 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 6AIIAJDf907222; Wed, 18 Nov 2026 13:10:19 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 sss.pgh.pa.us 6AIIAJDf907222 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sss.pgh.pa.us; s=default; t=1795025419; bh=xxwzHOzyB0lec5YM2cmi3+up3S0Tn/ReorvpLA/BEto=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=pPw8/25glsnbH6YlvUxkBsQEABTuS9tJmNCE3lW3FI2ZXaldvS29vand5VSIRVXS5 uSALtWcRcdLKy+/dCnYQtde+H8t/ftiHhz56LDOrGxEP705lH4oubzWrZWkrLFSlix phWAU03Ye6HsWzLOrqp3gevta0s2vuE8eKUQ4eaA= From: Tom Lane To: miracee cc: pgsql-bugs@lists.postgresql.org Subject: Re: Inconsistent time zone handling in timetz In-reply-to: References: Comments: In-reply-to miracee message dated "Wed, 18 Nov 2026 11:56:24 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <907220.1795025419.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 18 Nov 2026 13:10:19 -0500 Message-ID: <907221.1795025419@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk miracee writes: > # SELECT '10:00 CET'::timetz; > timetz > ------------- > 10:00:00+01 > (1 row) > # SELECT '10:00 Europe/Berlin'::timetz; > ERROR: invalid input syntax for type time with time zone: "10:00 Europe/= Berlin" > LINE 1: SELECT '10:00 Europe/Berlin'::timetz; This is documented, no? [1] ... You can also specify a date but it will be ignored, except when you use a time zone name that involves a daylight-savings rule, such as America/New_York. In this case specifying the date is required in order to determine whether standard or daylight-savings time applies. The appropriate time zone offset is recorded in the time with time zone value and is output as stored; it is not adjusted to the active time zone. I'd agree that the error message is pretty nonspecific :-(. However, the view this project takes is that timetz is a type with little if any real-world use, so we're unlikely to put much effort into making it more user-friendly. regards, tom lane [1] https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYP= E-DATETIME-INPUT-TIMES