On Jun 22, 2024, at 14:10, David E. Wheeler wrote:
> I believe the former issue is caused by the latter: The jsonpath
> implementation uses the formatting strings to parse the timestamps[1], and
> since there is no formatting to support offsets with seconds, it doesn’t work
> at all in JSON
On Jun 22, 2024, at 13:15, Tom Lane wrote:
> It's hard to get excited about this.
I freely admit I’m getting into the weeds here. :-)
>> The corresponding jsonpath methods don’t like offsets with seconds *at all*:
>
> Perhaps that should be fixed, but it's pretty low-priority IMO.
> I doubt
"David E. Wheeler" writes:
> The treatment of timestamptz (and timetz) values with offsets that include
> seconds seems a bit inconsistent.
It's hard to get excited about this. Per the IANA TZ data,
nowhere in the world has used fractional-minute UT offsets
since 1972:
# In 1972 Liberia was
Hackers,
The treatment of timestamptz (and timetz) values with offsets that include
seconds seems a bit inconsistent. One can create such timestamps through the
input function:
david=# select '2024-06-22T12:35:00+02:30:15'::timestamptz;
timestamptz
