Date: Tue, 26 Sep 2023 19:24:22 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: davecramer@postgres.rocks, pgsql-docs@lists.postgresql.org
Subject: Re: Incorrect/confusing information about timetz
Message-ID: <ZRNoJps0Zsd3KwsB@momjian.us>
References: <168451942371.714.9173574930845904336@wrigleys.postgresql.org>
 <ZPozoUwxa80aarQp@momjian.us>
 <1757505.1694119308@sss.pgh.pa.us>
 <ZPo6C2s9PDAwfKeS@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZPo6C2s9PDAwfKeS@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/ZRNoJps0Zsd3KwsB%40momjian.us>
Precedence: bulk

On Thu, Sep  7, 2023 at 05:00:59PM -0400, Bruce Momjian wrote:
> On Thu, Sep  7, 2023 at 04:41:48PM -0400, Tom Lane wrote:
> > 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."
> 
> Yeah, there is no mention of it odd output behavior.  Here is a patch to
> add that.

Patch applied back to Postgres 11.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.