Horton

Re: First draft of PG 17 release notes

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-05-09T16:29:38Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Revert support for ALTER TABLE ... MERGE/SPLIT PARTITION(S) commands

  2. When creating materialized views, use REFRESH to load data.

  3. Revert temporal primary keys and foreign keys

  4. Avoid needless large memcpys in libpq socket writing

  5. Enhance nbtree ScalarArrayOp execution.

  6. Introduce a non-recursive JSON parser

  7. Combine freezing and pruning steps in VACUUM

  8. Allow SIGINT to cancel psql database reconnections.

  9. Provide API for streaming relation data.

  10. Add hash support functions and hash opclass for contrib/ltree.

  11. Pull up ANY-SUBLINK with the necessary lateral support.

  12. Read WAL directly from WAL buffers.

  13. Introduce the dynamic shared memory registry.

  14. Add macros for looping through a List without a ListCell.

  15. Support +/- infinity in the interval data type.

  16. Extend ALTER OPERATOR to allow setting more optimization attributes.

  17. Consider cheap startup paths in add_paths_to_append_rel

On Thu, May  9, 2024 at 12:10:11PM -0400, Andrew Dunstan wrote:
> 
> On 2024-05-09 Th 00:03, 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
> 
>     It will be improved until the final release.  The item count is 188,
>     which is similar to recent releases:
> 
>             release-10:  189
>             release-11:  170
>             release-12:  180
>             release-13:  178
>             release-14:  220
>             release-15:  184
>             release-16:  206
>             release-17:  188
> 
>     I welcome feedback.  For some reason it was an easier job than usual.
> 
> 
>   • Remove the ability to build Postgres with Visual Studio (Michael Paquier)
> 
>     Meson is now the only available Windows build method.
> 
> 
> This is a category mistake. What was removed was the special code we had for
> building with VS, but not the ability to build with VS. You can build with VS
> using meson (see for example drongo on the buildfarm)

Wow, okay, I am not surprised I was confused.  New text is:

	<!--
	Author: Michael Paquier <michael@paquier.xyz>
	2023-12-20 [1301c80b2] Remove MSVC scripts
	-->
	
	<listitem>
	<para>
	Remove the Microsoft Visual Studio Studio-specific Postgres build option (Michael Paquier)
	</para>
	
	<para>
	Meson is now the only method for Visual Studio builds.
	</para>
	</listitem>
	<!--
	Author: Michael Paquier <michael@paquier.xyz>
	2023-12-20 [1301c80b2] Remove MSVC scripts
	-->
	
	<listitem>
	<para>
	Remove the Microsoft Visual Studio Studio-specific Postgres build option (Michael Paquier)
	</para>
	
	<para>
	Meson is now the only method for Visual Studio builds.
	</para>
	</listitem>

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

  Only you can decide what is important to you.