Re: First draft of PG 19 release notes - Mailing list pgsql-hackers

From jian he
Subject Re: First draft of PG 19 release notes
Date
Msg-id CACJufxG1UN2fMQ=TZvxo4B7ZufhCj8UBn4ptA3NbOWA9ER=PCQ@mail.gmail.com
Whole thread
In response to First draft of PG 19 release notes  (Bruce Momjian <bruce@momjian.us>)
Responses Re: First draft of PG 19 release notes
List pgsql-hackers
On Wed, Apr 15, 2026 at 9:19 AM Bruce Momjian <bruce@momjian.us> wrote:
>
> I have completed the first draft of the PG 19 release notes:
>
>         https://www.postgresql.org/docs/devel/release-19.html
>

https://git.postgresql.org/cgit/postgresql.git/commit/?id=ecd9288624a1582a732cf86ac5a01475a1ce7815
https://git.postgresql.org/cgit/postgresql.git/commit/?id=4edd6036d69ce42ac1af236f659f20daed65c8d4
Do you think these two are worth adding to the release notes?

"""
Allow COPY TO to output partitioned tables (Jian He, Ajin Cherian) § §
Previously COPY (SELECT ...) has to be used to output partitioned tables.
"""
The second commit uses this feature, so i guess the commit message
needs a slight change.

"""
Improve timing performance measurements (Lukas Fittl, Andres Freund,
David Geier, Lukas Fittl, David Geier) § §
This benefits EXPLAIN (ANALYZE, TIMING) and pg_test_timing, and is
controlled via server variable timing_clock_source.
"""
Duplicated name entry.

"""
Allow IS [NOT] DISTINCT FROM NULL to be converted to IS [NOT] NULL for
proven null arguments (Richard Guo) §
The latter form is more easily optimized.
"""
Two optional ``[NOT]`` introduce ambiguity.

"""
Add support for INSERT ... RETURNING ... ON CONFLICT DO SELECT
(Andreas Karlsson, Marko Tiikkaja, Viktor Holmberg) §
This allows conflicting rows to be returns, and optionally locked with
FOR UPDATE/SHARE.
"""
I think it's:
INSERT... ON CONFLICT DO SELECT...RETURNING



--
jian
https://www.enterprisedb.com/



pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: Adding REPACK [concurrently]
Next
From: Andres Freund
Date:
Subject: Re: Adding REPACK [concurrently]