From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: davecramer@postgres.rocks, pgsql-docs@lists.postgresql.org
Subject: Re: Incorrect/confusing information about timetz
In-reply-to: <ZPozoUwxa80aarQp@momjian.us>
References: <168451942371.714.9173574930845904336@wrigleys.postgresql.org>
 <ZPozoUwxa80aarQp@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Thu, 07 Sep 2023 16:33:37 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1757504.1694119308.1@sss.pgh.pa.us>
Date: Thu, 07 Sep 2023 16:41:48 -0400
Message-ID: <1757505.1694119308@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1757505.1694119308%40sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> Uh, yes to the storage part, no to the output part.  ;-)  Postgres does
> store the timetz time zone offset, but it doesn't adust it once it is
> stored so doesn't adjust for the session time zone:

Right, it just stores a numeric UTC offset.

> Do we want to document this?

Section 8.5.1.2. Times already says "The appropriate time zone offset
is recorded in the time with time zone value."  Maybe that could be
made a little more precise, say "The resolved numeric offset from UTC
is recorded in the time with time zone value."

			regards, tom lane