Re: Linkify mentions of the primary/subscriber's max_replication_slots
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Tristan Partin <tristan@partin.io>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-11-11T11:53:45Z
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 →
-
Doc: Add links to clarify the max_replication_slots.
- 220cea9411e6 18.0 landed
On Thu, Nov 7, 2024 at 4:40 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Thu, Nov 7, 2024 at 9:36 AM Tristan Partin <tristan@partin.io> wrote: > > > > > > Here is a patch which does so. > > > > <para> > Note that this parameter also applies on the subscriber side, but with > - a different meaning. > + a different meaning. See <xref > linkend="guc-max-replication-slots-subscriber"/> > + in <xref linkend="runtime-config-replication-sender"/> for more > + details. > </para> > </listitem> > </varlistentry> > @@ -5215,7 +5217,9 @@ ANY <replaceable > class="parameter">num_sync</replaceable> ( <replaceable class=" > > <para> > Note that this parameter also applies on a sending server, but with > - a different meaning. > + a different meaning. See <xref linkend="guc-max-replication-slots"/> > + in <xref linkend="runtime-config-replication-primary"/> for more > + details. > > <xref linkend="runtime-config-replication-sender"/> and <xref > linkend="runtime-config-replication-primary"/> are incorrect. They > should be instead <xref > linkend="runtime-config-replication-subscriber"/> and <xref > linkend="runtime-config-replication-sender"/>. > I have made the required changes and pushed the patch. -- With Regards, Amit Kapila.