Re: First draft of PG 17 release notes

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "Jonathan S. Katz" <jkatz@postgresql.org>, Laurenz Albe <laurenz.albe@cybertec.at>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-10-10T03:06:09Z
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 Tue, Oct  8, 2024 at 11:57:19AM +0530, Amit Kapila wrote:
> On Tue, Oct 8, 2024 at 6:25 AM Bruce Momjian <bruce@momjian.us> wrote:
> >
> > On Sun, Sep 29, 2024 at 06:33:29PM +0530, Amit Kapila wrote:
> > > > > It is better to write the above statement as:
> > > > > "pg_upgrade</application></link> now preserves replication slots on
> > > > > publishers and full subscription's state on subscribers". This is
> > > > > because replication slots are preserved on publishers. The subscribers
> > > > > preserve the subscription state.
> > > >
> > > > So, as I understand it, this preservation only happens when the _old_
> > > > Postgres version is 17+.
> > > >
> > >
> > > Yes.
> > >
> > > >  Do we want to try and explain that in the
> > > > Postgres 17 release notes?
> > > >
> > >
> > > It would be good if we can capture that information without bloating
> > > the release document. However, this information is already present in
> > > pg_upgrade docs, so users have a way to know the same even if we can't
> > > mention it in the release notes.
> >
> > I have developed the attached patch to mention it is "logical" slots,
> > and to mention its future use.
> >
> 
> LGTM. Thanks!

Great, patch applied.

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

  When a patient asks the doctor, "Am I going to die?", he means 
  "Am I going to die soon?"