Horton

Re: First draft of PG 17 release notes

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
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-09-26T09:38:52Z
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 Sat, Sep 21, 2024 at 1:50 AM Bruce Momjian <bruce@momjian.us> wrote:
>
> On Fri, Sep 20, 2024 at 04:05:11PM -0400, Tom Lane wrote:
> > Bruce Momjian <bruce@momjian.us> writes:
> > > Patch applied to PG 17.
> >
> > I don't see a push?
>
> Push was delayed because my test script found some uncommitted files due
> to earlier testing.  Should be fine now.
>

<para>
         <link
          linkend="app-pgcreatesubscriber"><application>pg_createsubscriber</application></link>,
          a utility that creates logical replicas from physical standbys
        </para>

This description is okay but according to me, the more compelling use
case is that this new utility helps to allow online upgrades of
physical replication setup as explained in the blog [1]. See the
section: "Upgrading Streaming (Physical) Replication Setup".

       </listitem>
       <listitem>
        <para>
         <link
          linkend="pgupgrade"><application>pg_upgrade</application></link> now
          preserves replication slots on both publishers and subscribers
        </para>

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.

[1] - http://amitkapila16.blogspot.com/2024/09/online-upgrading-logical-and-physical.html

-- 
With Regards,
Amit Kapila.