First draft of PG 17 release notes

On Thu, 9 May 2024 at 16:04, Bruce Momjian <bruce@momjian.us> wrote:

I welcome feedback. For some reason it was an easier job than usual.

Thanks for working on that.

+2023-11-02 [cac169d68] Increase DEFAULT_FDW_TUPLE_COST from 0.01 to 0.2

+Double the default foreign data wrapper tuple cost (David Rowley, Umair Shahid)

That's 20x rather than 2x.

David

Hi Bruce,

A minor formatting issue in the start below. Bullet is not required here.

E.1.1. Overview
<https://momjian.us/pgsql_docs/release-17.html#RELEASE-17-HIGHLIGHTS&gt;

PostgreSQL 17 contains many new features and enhancements, including:

-

The above items and other new features of PostgreSQL 17 are explained in
more detail in the sections below.
Regards,
Ikram

On Thu, May 9, 2024 at 9:45 AM David Rowley <dgrowleyml@gmail.com> wrote:

On Thu, 9 May 2024 at 16:04, Bruce Momjian <bruce@momjian.us> wrote:

I welcome feedback. For some reason it was an easier job than usual.

Thanks for working on that.

+2023-11-02 [cac169d68] Increase DEFAULT_FDW_TUPLE_COST from 0.01 to 0.2

+Double the default foreign data wrapper tuple cost (David Rowley, Umair

Shahid)

That's 20x rather than 2x.

David

--
Muhammad Ikram

On Thu, 9 May 2024 at 16:47, Muhammad Ikram <mmikram@gmail.com> wrote:

A minor formatting issue in the start below. Bullet is not required here.

This is a placeholder for the highlight features of v17 will go.
Bruce tends not to decide what those are all by himself.

David

Hi,

On Thu, May 09, 2024 at 12:03:50AM -0400, Bruce Momjian wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

Thanks for working on that!

I welcome feedback.

Add system view pg_wait_events that reports wait event types (Michael Paquier)

Michael is the committer for 1e68e43d3f, the author is me.

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Hi,

On Thu, May 9, 2024 at 1:03 PM Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

Thank you for working on that!

I'd like to mention some of my works. I think we can add the vacuum
performance improvements by the following commits:

- Add template for adaptive radix tree (ee1b30f1)
- Add TIDStore, to store sets of TIDs (ItemPointerData) efficiently (30e144287)
- Use TidStore for dead tuple TIDs storage during lazy vacuum (667e65aac)

Also, please consider the following item:

- Improve eviction algorithm in ReorderBuffer using max-heap for many
subtransactions (5bec1d6bc)

Finally, should we mention the following commit in the release note?
It's not a user-visible change but added a new regression test module.

- Add tests for XID wraparound (e255b646a)

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

On Thu, May 9, 2024 at 12:04 PM Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

Thanks for working on that.

For this item:

Allow the optimizer to improve CTE plans by using the sort order of
columns referenced in earlier CTE clauses (Jian Guo)

I think you mean a65724dfa. The author should be 'Richard Guo'.

And I'm wondering if it is more accurate to state it as "Allow the
optimizer to improve plans for the outer query by leveraging the sort
order of a CTE's output."

I think maybe a similar revision can be applied to the item just above
this one.

Thanks
Richard

Hi,

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

It will be improved until the final release. The item count is 188,
which is similar to recent releases:

Thanks for working on this.

I believe the part of the 64-bit XIDs patchset that was delivered in
PG17 is worth highlighting in "E.1.3.10. Source Code" section:

4ed8f0913bfd
2cdf131c46e6
5a1dfde8334b
a60b8a58f435

All this can probably be summarized as one bullet "Index SLRUs by
64-bit integers rather than by 32-bit ones" where the authors are:
Maxim Orlov, Aleksander Alekseev, Alexander Korotkov, Teodor Sigaev,
Nikita Glukhov, Pavel Borisov, Yura Sokolov.

--
Best regards,
Aleksander Alekseev

On Thu, May 9, 2024 at 12:04 PM Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

another potential incompatibilities issue:
ALTER TABLE DROP PRIMARY KEY

see:
/messages/by-id/202404181849.6frtmajobe27@alvherre.pgsql

Bruce Momjian <bruce@momjian.us> writes:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

My name is listed twice in the "Improve psql tab completion" item.

- ilmari

Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> writes:

Bruce Momjian <bruce@momjian.us> writes:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

My name is listed twice in the "Improve psql tab completion" item.

You can move one of them to "Track DEALLOCATE in pg_stat_statements",
which Michael and I co-authored.

- ilmari

On Thu, May 9, 2024 at 12:04 PM Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

* Add function pg_buffercache_evict() to allow shared buffer eviction
(Palak Chaturvedi, Thomas Munro)
* This is useful for testing.

this should put it on the section
< E.1.3.11. Additional Modules
?

Then I found out official release notes don't have <section> attributes,
so it doesn't matter?

<<
Allow ALTER OPERATOR to set more optimization attributes (Tommy Pavlicek)
This is useful for extensions.
<<
I think this commit title "Add hash support functions and hash opclass
for contrib/ltree."
from [1]https://git.postgresql.org/cgit/postgresql.git/commit/?id=485f0aa85995340fb62113448c992ee48dc6fff1 is more descriptive.
i am not 100% sure of the meaning of "This is useful for extensions."

[1]: https://git.postgresql.org/cgit/postgresql.git/commit/?id=485f0aa85995340fb62113448c992ee48dc6fff1

<<
Allow ALTER OPERATOR to set more optimization attributes (Tommy Pavlicek)
This is useful for extensions.
<<

sorry, I mean
<<
Allow the creation of hash indexes on ltree columns (Tommy Pavlicek)
This also enables hash join and hash aggregation on ltree columns.
<<

better description would be:
<<
Add hash support functions and hash opclass for contrib/ltree (Tommy Pavlicek)
This also enables hash join and hash aggregation on ltree columns.
<<

Some findings

1.

Remove adminpack contrib extension (Daniel Gustafsson)

This was used by non-end-of-life pgAdmin III.

Perhaps you mean now-end-of-life (s/non/now/)

2.

All specification of partitioned table access methods (Justin Pryzby, >>Soumyadeep Chakraborty, Michael Paquier)

perhaps you mean Allow, otherwise meaning not clear.

3.

Add some long options to pg_archivecleanup (Atsushi Torikoshi)
The long options are --debug, --dry-run, and /--strip-extension.

The slash should be omitted.

Hans Buschmann

On Thu, May 9, 2024 at 6:53 PM jian he <jian.universality@gmail.com> wrote:

On Thu, May 9, 2024 at 12:04 PM Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

< Add columns to pg_stats to report range histogram information (Egor
Rogov, Soumyadeep Chakraborty)
I think this applies to range type and multi range type, "range
histogram information" seems not very clear to me.
So maybe:
< Add columns to pg_stats to report range-type histogram information
(Egor Rogov, Soumyadeep Chakraborty)

Display length and bounds histograms in pg_stats
< Add new COPY option "ON_ERROR ignore" to discard error rows (Damir
Belyalov, Atsushi Torikoshi, Alex Shulgin, Jian He, Jian He, Yugo
Nagata)
duplicate name.

On Thu, May 9, 2024 at 04:44:47PM +1200, David Rowley wrote:

On Thu, 9 May 2024 at 16:04, Bruce Momjian <bruce@momjian.us> wrote:

I welcome feedback. For some reason it was an easier job than usual.

Thanks for working on that.

+2023-11-02 [cac169d68] Increase DEFAULT_FDW_TUPLE_COST from 0.01 to 0.2

+Double the default foreign data wrapper tuple cost (David Rowley, Umair Shahid)

That's 20x rather than 2x.

Oops, changed to:

Increase the default foreign data wrapper tuple cost (David
Rowley, Umair Shahid)

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

On Thu, May 9, 2024 at 09:47:34AM +0500, Muhammad Ikram wrote:

Hi Bruce,

A minor formatting issue in the start below. Bullet is not required here.

E.1.1. Overview 

PostgreSQL 17 contains many new features and enhancements, including:

•

The above items and other new features of PostgreSQL 17 are explained in more
detail in the sections below.

That is just a place-holder. I changed the bullet text to be:

TO BE COMPLETED LATER

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

On Thu, May 9, 2024 at 04:52:14PM +1200, David Rowley wrote:

On Thu, 9 May 2024 at 16:47, Muhammad Ikram <mmikram@gmail.com> wrote:

A minor formatting issue in the start below. Bullet is not required here.

This is a placeholder for the highlight features of v17 will go.
Bruce tends not to decide what those are all by himself.

Yes, I already have so much of my opinion in the release notes that I
prefer others to make that list, and to make the Acknowledgments list
at the bottom.

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

On Thu, May 9, 2024 at 04:53:38AM +0000, Bertrand Drouvot wrote:

Hi,

On Thu, May 09, 2024 at 12:03:50AM -0400, Bruce Momjian wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

Thanks for working on that!

I welcome feedback.

Add system view pg_wait_events that reports wait event types (Michael Paquier)

Michael is the committer for 1e68e43d3f, the author is me.

Wow, thank you for finding that. The commit message is very clear so I
don't know how I made that mistake. Fixed.

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

On Thu, May 9, 2024 at 02:17:12PM +0900, Masahiko Sawada wrote:

Hi,

On Thu, May 9, 2024 at 1:03 PM Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the PG 17 release notes; you can
see the results here:

https://momjian.us/pgsql_docs/release-17.html

Thank you for working on that!

I'd like to mention some of my works. I think we can add the vacuum
performance improvements by the following commits:

- Add template for adaptive radix tree (ee1b30f1)
- Add TIDStore, to store sets of TIDs (ItemPointerData) efficiently (30e144287)
- Use TidStore for dead tuple TIDs storage during lazy vacuum (667e65aac)

Okay, I reworded the item, added authors, and added the commits:

<!--
Author: John Naylor <john.naylor@postgresql.org>
2024-03-07 [ee1b30f12] Add template for adaptive radix tree
Author: Masahiko Sawada <msawada@postgresql.org>
2024-03-21 [30e144287] Add TIDStore, to store sets of TIDs (ItemPointerData) ef
Author: Masahiko Sawada <msawada@postgresql.org>
2024-04-02 [667e65aac] Use TidStore for dead tuple TIDs storage during lazy vac
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
2024-04-03 [6dbb49026] Combine freezing and pruning steps in VACUUM
-->

<listitem>
<para>
Allow vacuum to more efficiently remove and freeze tuples (John Naylor, Masahiko Sawada, Melanie Plageman)
</para>
</listitem>

Also, please consider the following item:

- Improve eviction algorithm in ReorderBuffer using max-heap for many
subtransactions (5bec1d6bc)

I looked at that item and I don't have a generic "make logical
replication apply faster" item to merge it into, and many
subtransactions seemed like enough of an edge-case that I didn't think
mentioning it make sense. Can you see a good place to add it?

Finally, should we mention the following commit in the release note?
It's not a user-visible change but added a new regression test module.

- Add tests for XID wraparound (e255b646a)

I don't normally add testing infrastructure changes unless they are
major.

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.