Re: First draft of PG 19 release notes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: First draft of PG 19 release notes
Date: 2026-07-19 00:50:24
Message-ID: alwfUMjJ8NADFEF9@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 18, 2026 at 06:03:09AM +0800, Chao Li wrote:
> Hi Bruce,
>
> This feature has been reverted by 372b8d1adb76740123791e9ded4f665b175f5bf5, so you need to delete the item from the v19 release note.
>
> <!--
> Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> 2025-09-29 [ef38a4d97] Add GROUP BY ALL.
> -->

I have updated the release notes to match current git; updated output
is at:

https://momjian.us/pgsql_docs/

Patch attached. I added the psql \crosstabview item as an
incompatibility. I didn't add this commit:

commit 0c15b715c65
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Tue Jun 30 17:21:23 2026 -0400

Disallow set-returning functions within window OVER clauses.

We previously allowed this, but it leads to odd behaviors, basically
because putting a SRF there is inconsistent with the principle that a
window function doesn't change the number of rows in the query result.
There doesn't seem to be a strong reason to try to make such cases
behave consistently. Users should put their SRFs in lateral FROM
clauses instead.

This issue has been sitting on the back burner for multiple years
now, partially because it didn't seem wise to back-patch such a
change. Let's squeeze it into v19 before it's too late.

because I assumed its use was rare enough and the error message clear
enough.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

Attachment Content-Type Size
REL_19_STABLE.diff text/x-diff 3.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-07-19 01:39:13 Re: REASSIGN OWNED vs. relisshared dep on !relisshared
Previous Message 신성준 2026-07-18 23:33:18 Re: Row pattern recognition