MIME-Version: 1.0
References: <501040.1772433449@sss.pgh.pa.us> <CAMbWs49P2z40f5yb_97ErwtC9ocdR5QQN0gWUZtjgot9+iGAcg@mail.gmail.com>
 <CAMbWs4-NuYP+0Zq9=Ufwy5GcM0XQnEqWjJFucaRGO4EQgiCcow@mail.gmail.com>
 <CAMbWs4-ra9mkBhUs2kmB5KxWuo80oAA33gZ=8JmRxmG3qGNxUg@mail.gmail.com>
 <CA+HiwqEtiTNV2v2P0HGa0B1TMNfmPweKXMZEOYPoQuFf3ZhsXQ@mail.gmail.com>
 <CAMbWs49tDE_niKLr4mzsa2BkX7fkWrorBzWheKTBziZ7z9-AuQ@mail.gmail.com>
 <CAMbWs48KEdgyJhxCOysaRdRJ5NzPObUET+5XbvyiqDfqyABEwg@mail.gmail.com>
 <485641.1776738632@sss.pgh.pa.us> <CAMbWs4_vqNEcHpvKFeFxfRoisrvw6yJ3styhS-arQDHZirw5cQ@mail.gmail.com>
 <CAMbWs49ps9eGWvkwc64ytUxdK0s-=xdFjtf64WyGp65EgTZ_LQ@mail.gmail.com> <aevLYeoSSgiwEiO-@nathan>
In-Reply-To: <aevLYeoSSgiwEiO-@nathan>
From: Melanie Plageman <melanieplageman@gmail.com>
Date: Thu, 30 Apr 2026 18:04:54 -0400
Message-ID: <CAAKRu_YU542L_+_H1VFSTtLnj4Yo=GcXykyiw_6GZZiOEt5mVA@mail.gmail.com>
Subject: Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC
 9075-2:2023(E) 6.34 <JSON value constructor>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Richard Guo <guofenglinux@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, 
	Amit Langote <amitlangote09@gmail.com>, Vik Fearing <vik@postgresfriends.org>, lukas.eder@gmail.com, 
	pgsql-bugs@lists.postgresql.org, rmt@lists.postgresql.org, 
	=?UTF-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>, 
	Heikki Linnakangas <hlinnaka@iki.fi>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAAKRu_YU542L_%2B_H1VFSTtLnj4Yo%3DGcXykyiw_6GZZiOEt5mVA%40mail.gmail.com>
Precedence: bulk

On Fri, Apr 24, 2026 at 3:58=E2=80=AFPM Nathan Bossart <nathandbossart@gmai=
l.com> wrote:
>
> On Thu, Apr 23, 2026 at 09:55:10AM +0900, Richard Guo wrote:
> >> Hi RMT,
> >>
> >> I'd like to commit a fix for JSON_ARRAY(subquery) behavior that
> >> involves a user-visible incompatibility, and would appreciate your
> >> go/no-go since we're past feature freeze.
> >>
> >> Summary:
> >>
> >> - JSON_ARRAY(SELECT ...) currently returns NULL over an empty result
> >> set, but the SQL/JSON standard requires it to return '[]'.  Fixing
> >> this changes user-visible output.
> >>
> >> - The same patch also fixes a deparsing issue: views defined with
> >> JSON_ARRAY(SELECT ...) are dumped back as the internal JSON_ARRAYAGG
> >> rewrite instead of the original syntax.
>
> I am fine with committing this for v19, assuming there is consensus on th=
e
> patch content.
>
> Heikki/Melanie: Any objections?

Nope. I'm +1 on committing this now. 19 is unreleased -- I see no
reason to wait a year.

- Melanie