Doc: Improve the wording of logical slot prerequisites.

Replace the previous negative phrasing such as "there are no slots whose
... is not true" with a direct expression that all slots must have
conflicting = false.

Similarly, reword the requirement on the new cluster to state that it must
not have any permanent logical slots, clarifying that any existing logical
slots must have temporary set to true.

These changes improve readability without altering the meaning.

Reported-by: <mimidatabase@gmail.com>
Author: Vignesh C <vignesh21@gmail.com>
Reviewed-by: David G. Johnston <david.g.johnston@gmail.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Discussion: https://postgr.es/m/177609278737.403059.14174275013090471947%40wrigleys.postgresql.org
This commit is contained in:
Amit Kapila 2026-04-17 15:02:15 +05:30
parent 950f50d5d4
commit f3ae1ec729

View file

@ -2785,18 +2785,17 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
</listitem>
<listitem>
<para>
All slots on the old cluster must be usable, i.e., there are no slots
whose
All slots on the old cluster must be usable, i.e., their
<link linkend="view-pg-replication-slots">pg_replication_slots</link>.<structfield>conflicting</structfield>
is not <literal>true</literal>.
is <literal>false</literal>.
</para>
</listitem>
<listitem>
<para>
The new cluster must not have permanent logical slots, i.e.,
there must be no slots where
The new cluster must not have any permanent logical slots; i.e., any
existing logical slots must have
<link linkend="view-pg-replication-slots">pg_replication_slots</link>.<structfield>temporary</structfield>
is <literal>false</literal>.
set to <literal>true</literal>.
</para>
</listitem>
</itemizedlist>