Doc: Fix incorrect reference to conflicting column in pg_replication_slots.
authorAmit Kapila <akapila@postgresql.org>
Mon, 29 Jan 2024 06:43:39 +0000 (12:13 +0530)
committerAmit Kapila <akapila@postgresql.org>
Mon, 29 Jan 2024 06:43:39 +0000 (12:13 +0530)
Commit 007693f2a3 changes the existing 'conflicting' field to
'conflict_reason' in pg_replication_slots but missed updating one of its
existing references.

Author: Hou Zhijie
Discussion: https://postgr.es/m/OS0PR01MB571690299199ACA80F602D97947E2@OS0PR01MB5716.jpnprd01.prod.outlook.com

doc/src/sgml/ref/pgupgrade.sgml

index 87be1fb1c2682a8a44ee6032298520dc336faff5..ae6d3c49a69164a84e0c3595ce6e7fe375f1d07f 100644 (file)
@@ -440,8 +440,8 @@ make prefix=/usr/local/pgsql.new install
       <para>
        All slots on the old cluster must be usable, i.e., there are no slots
        whose
-       <link linkend="view-pg-replication-slots">pg_replication_slots</link>.<structfield>conflicting</structfield>
-       is <literal>true</literal>.
+       <link linkend="view-pg-replication-slots">pg_replication_slots</link>.<structfield>conflict_reason</structfield>
+       is not <literal>NULL</literal>.
       </para>
      </listitem>
      <listitem>