Horton

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

Richard Guo <guofenglinux@gmail.com>

View thread View on postgr.es
From: Richard Guo <guofenglinux@gmail.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Vik Fearing <vik@postgresfriends.org>, lukas.eder@gmail.com, pgsql-bugs@lists.postgresql.org, Álvaro Herrera <alvherre@kurilemu.de>
Date: 2026-04-21T05:45:01Z
Lists: pgsql-bugs 
On Tue, Apr 21, 2026 at 12:57 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Tue, Apr 21, 2026 at 9:57 AM Richard Guo <guofenglinux@gmail.com> wrote:
> > (maybe we should place the multi-line comment above the field.)

> Makes sense. Perhaps we should also move the description of individual
> fields, where needed, into the comment above the struct definition
> like it is done for the nearby JsonValueExpr. Like this:

This looks even better.  I will take this approach.  Thanks!

- Richard

Commits

  1. Enforce RETURNING typmod for empty-set JSON_ARRAY(query)

  2. Fix JSON_ARRAY(query) empty set handling and view deparsing