Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: jsonpath: Inconsistency of timestamp_tz() Output
From: "David E. Wheeler" <david@justatheory.com>
In-Reply-To: <53E4B67F-70FF-441E-A48B-DE520966A312@justatheory.com>
Date: Tue, 9 Jul 2024 10:22:03 -0400
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B086E009-9D3F-422D-B281-E83FF2A548CB@justatheory.com>
References: <7DE080CE-6D8C-4794-9BD1-7D9699172FAB@justatheory.com>
 <CAEG8a3J2rBZ-S2VpwJCsWoLSmdSqWfnd0QH9kO_YE4ZJFSqGXQ@mail.gmail.com>
 <53E4B67F-70FF-441E-A48B-DE520966A312@justatheory.com>
To: Junwang Zhao <zhjwpku@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/B086E009-9D3F-422D-B281-E83FF2A548CB%40justatheory.com>
Precedence: bulk

On Jul 9, 2024, at 10:07, David E. Wheeler <david@justatheory.com> =
wrote:

> So perhaps I had things reversed before. Maybe it=E2=80=99s 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=E2=80=99s an inconsistency in the output of =
timestamp_tz() depending on whether the input has an offset or not. With =
offset:

david=3D# select jsonb_path_query_tz('"2024-08-15 12:34:56-05"', =
'$.timestamp_tz()');
     jsonb_path_query_tz    =20
-----------------------------
 "2024-08-15T12:34:56-05:00"

And without:

david=3D# select jsonb_path_query_tz('"2024-08-15 12:34:56"', =
'$.timestamp_tz()');
     jsonb_path_query_tz    =20
-----------------------------
 "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=E2=80=99t understand =
where the first example stores the offset.

Best,

David