From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: jsonpath: Inconsistency of timestamp_tz() Output |
Date: | 2024-07-09 14:22:03 |
Message-ID: | B086E009-9D3F-422D-B281-E83FF2A548CB@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 9, 2024, at 10:07, David E. Wheeler <david(at)justatheory(dot)com> wrote:
> So perhaps I had things reversed before. Maybe it’s actually doing the right then when it converts a timestamp to a timestamptz, but not when it the input contains an offset, as in your example.
To clarify, there’s an inconsistency in the output of timestamp_tz() depending on whether the input has an offset or not. With offset:
david=# select jsonb_path_query_tz('"2024-08-15 12:34:56-05"', '$.timestamp_tz()');
jsonb_path_query_tz
-----------------------------
"2024-08-15T12:34:56-05:00"
And without:
david=# select jsonb_path_query_tz('"2024-08-15 12:34:56"', '$.timestamp_tz()');
jsonb_path_query_tz
-----------------------------
"2024-08-15T16:34:56+00:00"
I suspect the latter is correct, given that the timestamptz type appears to be an int64, presumably always in UTC. I don’t understand where the first example stores the offset.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2024-07-09 14:35:09 | Re: Document DateStyle effect on jsonpath string() |
Previous Message | Joel Jacobson | 2024-07-09 14:11:22 | Re: Optimize numeric multiplication for one and two base-NBASE digit multiplicands. |