Re: Linkify mentions of the primary/subscriber's max_replication_slots

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Tristan Partin <tristan(at)partin(dot)io>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Linkify mentions of the primary/subscriber's max_replication_slots
Date: 2024-11-07 11:10:51
Message-ID: CAA4eK1KnmuCkt=sqmdJ9RNxfZ-PPWuGvO6n-2utb7peb0oS-Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 7, 2024 at 9:36 AM Tristan Partin <tristan(at)partin(dot)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"/>.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2024-11-07 11:42:30 Re: Add missing tab completion for ALTER TABLE ADD COLUMN IF NOT EXISTS
Previous Message Tender Wang 2024-11-07 11:07:35 Unsafe access BufferDescriptors array in BufferGetLSNAtomic()