Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wD1bG-002X0H-17 for pgsql-docs@arkaria.postgresql.org; Wed, 15 Apr 2026 14:52:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wD1bF-0004Jl-22 for pgsql-docs@arkaria.postgresql.org; Wed, 15 Apr 2026 14:52:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wCIsV-007XYa-16 for pgsql-docs@lists.postgresql.org; Mon, 13 Apr 2026 15:07:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wCIsS-00000000ogV-39wW for pgsql-docs@lists.postgresql.org; Mon, 13 Apr 2026 15:07:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=t1HUs2zchK8tHyQUqoQxCvdDinM4MlOUfJ6Qe8Zsoeg=; b=ZhS+zwkDYgjkGTY88GVveT6PCh eed45f7r6B7neoLzZACkWhZI3nuFUrxV33icFGadX8l7L3EZrfnpz2JqH2HcGdaFXrZi3pPB2b4PL 2Kz+x+U1dnP+S0S44mjIaVG3Tobo0uY9wP1rO+RmUQwlcNvE1YLKN49fmKQYaBD+CJS2qXIF9kgba AAVqHSQzkwVdjwceDJRm5z4V1So0isSwGC+h2UbxqFbOyF3SrefP2xdlKsKXrcdYAEhjtOg/YQ89g 91rSuLeeiNbh/Kv5Xr3cts6jJ8MVVuC/VUfmrVyvb9EJ0MfeJMELv2QcR+FHVQmTQMv/Q40XejLnH JGOvceTA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wCIsS-002QPz-0a for pgsql-docs@lists.postgresql.org; Mon, 13 Apr 2026 15:07:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wCIsQ-004zOH-2X for pgsql-docs@lists.postgresql.org; Mon, 13 Apr 2026 15:07:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Logical Replication upgrade To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: mimidatabase@gmail.com Reply-To: mimidatabase@gmail.com, pgsql-docs@lists.postgresql.org Date: Mon, 13 Apr 2026 15:06:27 +0000 Message-ID: <177609278737.403059.14174275013090471947@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/logical-replication-upgrade.html Description: Hello there, I don't know if it's me but I find this sentence quite confusing in its current wording: All slots on the old cluster must be usable, i.e., there are no slots whose pg_replication_slots.conflicting is not true. The prerequisite is that no replication slot has conflicting=3Dtrue right? So this sentence (the i.e. part) suggests the opposite, as per my understanding. Here is the link (29.13.1): https://www.postgresql.org/docs/current/logical-replication-upgrade.html#ST= EPS-TWO-NODE-CIRCULAR-LOGICAL-REPLICATION-CLUSTER:~:text=3Dthere%20are%20no= %20slots%20whose%20pg_replication_slots.conflicting%20is%20not%20true Thanks. Regards,