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 1wNUoj-000r2P-3C for pgsql-docs@arkaria.postgresql.org; Thu, 14 May 2026 12:05:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wNUoi-00C0Qm-2I for pgsql-docs@arkaria.postgresql.org; Thu, 14 May 2026 12:05:28 +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 1wNUoi-00C0Qb-1S for pgsql-docs@lists.postgresql.org; Thu, 14 May 2026 12:05:28 +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 1wNUog-00000000WqM-0guc for pgsql-docs@lists.postgresql.org; Thu, 14 May 2026 12:05:27 +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=tqZaFicgYOm1V9QR/bIPDonPAojvIsYEqH6gXrvAgtw=; b=bZcc1 oovt3HDrV8saSDIDUwEZQC7nJGvjkIld5s/a8m/yBa2tysY5ozu0CWCVMhTgD5S02kNarLnSk3+gI nrSZ3zDicn2tTIVGsI6sIHn1Kn/aZlCbJ++Fm/xP58J6lOiqsFGGVbRyJkdV67J72iB+w8hO6vCJg fD+C3yQ3OiZWdMNncD5wZa90oWf/mC6sQNgz50v6DSUQ6TNaDQlgmCGeMo5AECBSypIbv5cpWUMsb pOB6/r19vmyhU7u/IOcQ8tIOZYKOB42hGE4vJbjXYXOkyHyZuK/tkFz90bt5G4dSpYf9grRno3gyc VAOa7bRnsbOsAB4JosuK4VCrNjIsQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wNUod-0000000F2Ce-3GaO; Thu, 14 May 2026 08:05:23 -0400 Date: Thu, 14 May 2026 08:05:23 -0400 From: Bruce Momjian To: Robert Treat Cc: 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: <177685804902.403059.7237129094698721575@wrigleys.postgresql.org> 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 07:57:21AM -0400, Robert Treat wrote: > > I see your point. I went with adding the wording "no time zone > > adjustment" and "with time zone adjustment" in the table. Patch > > attached. You can see the output at: > > The quibble I have with the term "time zone adjustment" is that it > implies there will be some adjustment, but while you can change your > timezone preferences to display a timestamptz value in whatever time > zone you want, the value itself is never adjusted; it is stored as a > universal moment in time that doesn't change, regardless of the window > dressing around it. For this reason I have taken to describing that > difference between the two as that timestamptz stores the date and > time with timezone awareness, and timestamp is date and time with no > timezone awareness. Perhaps that might work better here as well? I used "adjustment" because the value is adjusted on input, and adjusted on output. I would say the value is not "aware" of the time zone because once it is internally stored as UTC it is no longer aware of the original time zone. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.