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-10 14:54:27 |
Message-ID: | 31EE4A0B-3126-43E3-9E24-998431241739@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 10, 2024, at 10:33, David E. Wheeler <david(at)justatheory(dot)com> wrote:
> Yeah I don’t know either, but now at least it’s consistent. I’ve attached a patch to fix it.
Actually I think there’s a subtlety still missing here:
@@ -2914,7 +2914,7 @@ HINT: Use *_tz() function for time zone support.
select jsonb_path_query_tz('"2023-08-15"', '$.timestamp_tz()'); -- should work
jsonb_path_query_tz -----------------------------
- "2023-08-15T07:00:00+00:00"
+ "2023-08-14T23:00:00-08:00"
(1 row)
This test runs while the time zone is set to “PST8PDT”, but it’s got the PST offset when it should be PDT:
david=# set time zone 'PST8PDT';
SET
david=# select '2023-08-15'::timestamptz;
timestamptz
------------------------
2023-08-15 00:00:00-07
So it should be -7, not -8. Not sure where to tell it to pay proper attention to daylight savings time.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Antonin Houska | 2024-07-10 15:00:13 | Missed opportunity for bsearch() in TransactionIdIsCurrentTransactionId()? |
Previous Message | Rafia Sabih | 2024-07-10 14:54:22 | Re: Possible incorrect row estimation for Gather paths |