Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Langote <amitlangote09(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, lukas(dot)eder(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
Date: 2026-04-24 12:04:03
Message-ID: CAMbWs4_CL1RE9dhYaG0aurmMawE5ectQzM52nVOY7UKyZ+6f2w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Apr 23, 2026 at 3:51 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Thu, Apr 23, 2026 at 09:55:10AM +0900, Richard Guo wrote:
> > Not sure the RMT mailing list works or not, maybe I'd better CC RMT
> > members.

> The mailing list you have attached is used every year by the RMT
> members for their internal discussions, attaching it to a
> pgsql-hackers or pgsql-bugs thread is not the usual practice, so I
> would suggest to avoid that in the future. Adding the RMT members
> directly in CC is enough if input is required for an open item.

Thanks for the information. Will avoid that in the future. Since the
RMT members are already in CC, I'll wait for their feedback.

- Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2026-04-24 12:44:04 Re: to_date()/to_timestamp() silently accept month=0 and day=0
Previous Message PG Bug reporting form 2026-04-24 11:56:38 BUG #19465: Inconsistency in EXP(LN(x)) equivalence leading to different COUNT result in PostgreSQL