| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First draft of PG 19 release notes |
| Date: | 2026-05-01 01:16:24 |
| Message-ID: | CAMbWs49Gepoq2g61gMBhS8QqcYGVk30yazEH2xP_Ysowd3wTwA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 15, 2026 at 10:19 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I have completed the first draft of the PG 19 release notes:
>
> https://www.postgresql.org/docs/devel/release-19.html
I just committed 8d829f5a0 to fix JSON_ARRAY(subquery) to return an
empty JSON array instead of NULL over an empty result set, per the
SQL/JSON standard. Since this is a user-visible behavior change, we
need to add an item to the v19 migration section to call it out.
Suggested entry:
- Make JSON_ARRAY(query_expression) return an empty JSON array when
the subquery returns no rows (Richard Guo)
Previously, an empty result set produced NULL. This corrects the
behavior to match the SQL/JSON standard. Application code that
relied on the previous NULL behavior may need to be updated.
- Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2026-05-01 01:30:00 | Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE |
| Previous Message | Amit Langote | 2026-05-01 01:13:57 | Re: ri_LockPKTuple misleading message |