From: Bruce Momjian <bruce@momjian.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: First draft of PG 17 release notes
Date: Mon, 7 Oct 2024 20:55:42 -0400
Message-ID: <ZwSDDm0bXAnHhk2F@momjian.us> (raw)
In-Reply-To: <CAA4eK1JjqNnPJLi58QdzGJ6=NQqctX+odXZvyO6oYPikU0WyDg@mail.gmail.com>
References: <ZjxLJpnH4VMkOMmi@momjian.us>
<0749f42a-17e1-42c9-a8d4-542fcb9fafeb@postgresql.org>
<7fd6ce37f6d14678b5024767aef7f8c5a414ba0c.camel@cybertec.at>
<d1748552-31f5-4f80-937b-767b5f7d8324@postgresql.org>
<Zu3UWHKwuzm-pVJo@momjian.us>
<2536416.1726862711@sss.pgh.pa.us>
<Zu3Y9ObRxWu8cUwm@momjian.us>
<CAA4eK1+bChgccySmcm0LbvkmBDJ3ufsLneF4iNa_aZ7t2P6=8w@mail.gmail.com>
<ZvirViPO4TJBmVxG@momjian.us>
<CAA4eK1JjqNnPJLi58QdzGJ6=NQqctX+odXZvyO6oYPikU0WyDg@mail.gmail.com>
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.
--
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?"
Attachments:REL_17_STABLE_pg_upgrade.diff (text/x-diff, 707B) downloaddiff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgmlindex eb65d1d725d..1e620d810d4 100644--- a/doc/src/sgml/release-17.sgml+++ b/doc/src/sgml/release-17.sgml@@ -63,7 +63,10 @@
<para>
<link
linkend="pgupgrade"><application>pg_upgrade</application></link> now
- preserves replication slots on both publishers and subscribers+ preserves logical replication slots on publishers and full+ subscription state on subscribers. This will allow upgrades+ to future major versions to continue logical replication without+ requiring copy to resynchronize.
</para>
</listitem>
</itemizedlist>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, amit.kapila16@gmail.com, tgl@sss.pgh.pa.us, jkatz@postgresql.org, laurenz.albe@cybertec.at
Subject: Re: First draft of PG 17 release notes
In-Reply-To: <ZwSDDm0bXAnHhk2F@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox