Re: First draft of PG 17 release notes

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: David Rowley <dgrowleyml@gmail.com>, Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Melanie Plageman <melanieplageman@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2024-05-24T03:27:04Z

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 Thu, May 23, 2024 at 11:11:10PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Thu, May 23, 2024 at 02:27:07PM +1200, David Rowley wrote:
> >> I also don't agree these should be left to "Source code" section. I
> >> feel that section is best suited for extension authors who might care
> >> about some internal API change.  I'm talking of stuff that makes some
> >> user queries possibly N times (!) faster. Surely "Source Code" isn't
> >> the place to talk about that?
> 
> > I said a new section "after our 'Source code' section," not in the
> > source code section.
> 
> Surely, if we make this a separate section, it would come before
> 'Source code'?
> 
> I am not sure Bruce that you realize that your disregard for
> performance improvements is shared by nobody.  Arguably,
> performance is 90% of what we do these days, and it's also
> 90% of what users care about.

Please stop saying I don't document performance.  I have already
explained enough which performance items I choose.  Please address my
criteria or suggest new criteria.

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

  Only you can decide what is important to you.