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.96) (envelope-from ) id 1wmD1m-000eXW-19 for pgsql-docs@arkaria.postgresql.org; Tue, 21 Jul 2026 16:09:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wmD1l-008GNv-3C for pgsql-docs@arkaria.postgresql.org; Tue, 21 Jul 2026 16:09:05 +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.96) (envelope-from ) id 1wmCzM-008F6d-1K for pgsql-docs@lists.postgresql.org; Tue, 21 Jul 2026 16:06:36 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wmCzJ-00000001I98-1WYS for pgsql-docs@lists.postgresql.org; Tue, 21 Jul 2026 16:06:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=flrnbUS88xkbILTOCMwx4/RJmfoRMWcFnGfbBcQQvoc=; b=4eIMh QyFcLQl4Li+S16dTC79v3NDthF3mO4V9ZdSwV+kv2JMPh9u+t400VOgo/iBFwZIOdobBfFH7JYwSI 7n4gOGAhpeC6g9ZBCYuQX4e1nm8/9A3ktm2tXejq7R12r/eVji2S4UH7loW70YuB41mE7E4cxo5Qo jb4KMg13tQY1CT+IOkW0Mb+x51KohPXjRsC64vGi9SK4EbrcOxbYs5UXhS++lLe4m5lvF3LDEj944 rNxt6dymqpYOHFrYMc5Kc9PCsQNihGtoPDRvVZAD0uODZ7QkoVJ+E/Qltgg6gnRrzxLI5CgJfKlsn KskB1QYOHiWecU/4mCq+rQw9d9pXA==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wmCzH-0000000FKpC-1bYX; Tue, 21 Jul 2026 12:06:31 -0400 Date: Tue, 21 Jul 2026 12:06:31 -0400 From: Bruce Momjian To: Tom Lane Cc: Dave Cramer , Robert Treat , Kirk Parker , Richard Neill , github@richardneill.org, pgsql-docs@lists.postgresql.org Subject: Re: Please clarify that Timestamp with Timezone doesn't preserve the timezone. Message-ID: References: <1018713.1778781735@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, May 14, 2026 at 03:46:14PM -0400, Bruce Momjian wrote: > On Thu, May 14, 2026 at 02:02:15PM -0400, Tom Lane wrote: > > Bruce Momjian writes: > > > Okay, here is the patch with "conversion". > > > > timetz does store a UTC offset, so it needs to be discussed separately. > > I don't think applying the same verbiage to time and timestamp will > > produce anything except more confusion. > > I see what you mean --- updated patch attached. > > If we want to be more explicit we could change "including time zone > conversion" to "including time zone conversion to/from UTC". Applied back to PG 19. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.