Re: jsonpath: Inconsistency of timestamp_tz() Output - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: jsonpath: Inconsistency of timestamp_tz() Output
Date
Msg-id B086E009-9D3F-422D-B281-E83FF2A548CB@justatheory.com
Whole thread Raw
In response to Re: jsonpath: Inconsistency of timestamp_tz() Output  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: jsonpath: Inconsistency of timestamp_tz() Output
List pgsql-hackers
On Jul 9, 2024, at 10:07, David E. Wheeler <david@justatheory.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’tunderstand where the first example stores the offset. 

Best,

David






pgsql-hackers by date:

Previous
From: "Joel Jacobson"
Date:
Subject: Re: Optimize numeric multiplication for one and two base-NBASE digit multiplicands.
Next
From: jian he
Date:
Subject: Re: Document DateStyle effect on jsonpath string()