From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ruslan <ruslan(at)d19i00d0skgddi(dot)cloudfront(dot)net> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Binary encoding of timetz type |
Date: | 2021-03-16 19:00:55 |
Message-ID: | 3388507.1615921255@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ruslan <ruslan(at)d19i00d0skgddi(dot)cloudfront(dot)net> writes:
> I wrote parser for COPY binary encoding. Everything is great but one thing
> worries me. It seems like the time offset field has reversed digit sign.
> I'm referring to this function
> https://github.com/postgres/postgres/blob/REL_13_STABLE/src/backend/utils/adt/date.c#L2150-L2159
Reversed compared to what? The code you quote is clearly sending the
internal representation as-is.
There's a lot of confusion in the world about whether positive timezone
offsets correspond to being east or west of Greenwich (not helped any
by the fact that there are relevant standards using both interpretations).
I think that our internal form uses positive-is-west, a/k/a POSIX rules,
but I'm too lazy to go check right now.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-03-16 22:18:15 | Re: SV: Log files polluted with permission denied error messages after every 10 seconds |
Previous Message | Peter Geoghegan | 2021-03-16 18:31:34 | Re: Postgres crashes at memcopy() after upgrade to PG 13. |