| 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:35:17 |
| Message-ID: | AC2FC8B4-A69B-4614-9D59-AB50ABA6B393@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.
>
> Ideally, I think, we wouldn’t convert the value and determine the offset twice, but teach date_timestamptz and timestamp_timestamptz (or date2timestamptz and timestamp2timestamptz?) how to return the offset, or create alternate functions that do so. Not sure what calling style should be adopted here, but this at least addresses the issue. Happy to resubmit something more efficient upon function design feedback.
Here’s a September CommitFest item, though I think it should be fixed before the next beta.
https://commitfest.postgresql.org/49/5119/
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-07-10 14:46:41 | Re: Add a GUC check hook to ensure summarize_wal cannot be enabled when wal_level is minimal |
| Previous Message | David E. Wheeler | 2024-07-10 14:33:05 | Re: jsonpath: Inconsistency of timestamp_tz() Output |