Re: jsonpath: Inconsistency of timestamp_tz() Output

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>

To: Jeevan Chalke <jeevan.chalke@enterprisedb.com>, "David E. Wheeler" <david@justatheory.com>

Cc: Junwang Zhao <zhjwpku@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-07-30T11:59:26Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix comment in libpqrcv_check_conninfo().
- 629520be5f9d 18.0 cited
Remove useless extern keywords
- 3fb59e789dd9 18.0 cited

On 2024-07-22 Mo 3:12 AM, Jeevan Chalke wrote:
>
>
> On Fri, Jul 19, 2024 at 7:35 PM David E. Wheeler 
> <david@justatheory.com> wrote:
>
>     On Jul 10, 2024, at 11:19, David E. Wheeler
>     <david@justatheory.com> wrote:
>
>     > Oh, and the time and date were wrong, too, because I blindly
>     used the same conversion for dates as for timestamps. Fixed in v2.
>     >
>     > PR: https://github.com/theory/postgres/pull/7
>     > CF: https://commitfest.postgresql.org/49/5119/
>
>     Rebase on 5784a49. No other changes. I would consider this a bug
>     in features added for 17.
>
>
> I agree with David that we need to set the tz explicitly as the 
> JsonbValue struct maintains that separately.
>
> However, in the attached version, I have added some comments and also, 
> fixed some indentation.
>

I have pushed this.


cheers


andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com