On Jul 9, 2024, at 10:07, David E. Wheeler <[email protected]> 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
