Re: Linkify mentions of the primary/subscriber's max_replication_slots - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Linkify mentions of the primary/subscriber's max_replication_slots
Date
Msg-id CAA4eK1KnmuCkt=sqmdJ9RNxfZ-PPWuGvO6n-2utb7peb0oS-Wg@mail.gmail.com
Whole thread Raw
List pgsql-hackers
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"/>.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Re: Incremental Sort Cost Estimation Instability
Next
From: Peter Eisentraut
Date:
Subject: Re: altering a column's collation leaves an invalid foreign key