| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | davecramer(at)postgres(dot)rocks, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Incorrect/confusing information about timetz |
| Date: | 2023-09-07 21:00:59 |
| Message-ID: | ZPo6C2s9PDAwfKeS@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Sep 7, 2023 at 04:41:48PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| Attachment | Content-Type | Size |
|---|---|---|
| timetz.diff | text/x-diff | 674 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-09-07 21:02:38 | Kernel settings shmall |
| Previous Message | Tom Lane | 2023-09-07 20:41:48 | Re: Incorrect/confusing information about timetz |