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 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
On Thu, Sep 7, 2023 at 04:41:48PM -0400, Tom Lane wrote:
> Bruce Momjian 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:
>
>
Bruce Momjian 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
On Fri, May 19, 2023 at 06:03:43PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/15/datatype-datetime.html
> Description:
>
> This statement in section 8.5.3 states
> "All timezone-aware dates
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/datatype-datetime.html
Description:
This statement in section 8.5.3 states
"All timezone-aware dates and times are stored internally in UTC. They are
converted to local time in the zone
