Re: First draft of PG 17 release notes

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>

To: Bruce Momjian <bruce@momjian.us>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2024-05-18T20:37:54Z

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 →

Revert support for ALTER TABLE ... MERGE/SPLIT PARTITION(S) commands
- 3890d90c1508 18.0 cited
When creating materialized views, use REFRESH to load data.
- b4da732fd64e 17.0 cited
Revert temporal primary keys and foreign keys
- 8aee330af55d 17.0 cited
Avoid needless large memcpys in libpq socket writing
- c4ab7da60617 17.0 cited
Enhance nbtree ScalarArrayOp execution.
- 5bf748b86bc6 17.0 cited
Introduce a non-recursive JSON parser
- 3311ea86edc7 17.0 cited
Combine freezing and pruning steps in VACUUM
- 6dbb490261a6 17.0 cited
Allow SIGINT to cancel psql database reconnections.
- cafe1056558f 17.0 cited
Provide API for streaming relation data.
- b5a9b18cd0bc 17.0 cited
Add hash support functions and hash opclass for contrib/ltree.
- 485f0aa85995 17.0 cited
Pull up ANY-SUBLINK with the necessary lateral support.
- 9f133763961e 17.0 cited
Read WAL directly from WAL buffers.
- 91f2cae7a4e6 17.0 cited
Introduce the dynamic shared memory registry.
- 8b2bcf3f287c 17.0 cited
Add macros for looping through a List without a ListCell.
- 14dd0f27d7cd 17.0 cited
Support +/- infinity in the interval data type.
- 519fc1bd9e9d 17.0 cited
Extend ALTER OPERATOR to allow setting more optimization attributes.
- 2b5154beab79 17.0 cited
Consider cheap startup paths in add_paths_to_append_rel
- a8a968a8212e 17.0 cited

On 2024-05-18 Sa 12:50, Bruce Momjian wrote:
> On Thu, May 16, 2024 at 11:50:20AM -0400, Andrew Dunstan wrote:
>>> Maybe "Introduce an incremental JSON parser" would have been a better
>>>> headline.
>>> Well, this gets into a level of detail that is beyond the average
>>> reader.  I think at that level people will need to read the git logs or
>>> review the code.  Do we use it for anything yet?
>>
>> Yes, certainly, it's used in handling backup manifests. Without it we can't
>> handle huge manifests. See commits ea7b4e9a2a and 222e11a10a.
>>
>> Other uses are in the works.
> Okay, added in the attached applied patch.
>

Thanks


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com