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 1w2pgo-000eEz-1P for pgsql-docs@arkaria.postgresql.org; Wed, 18 Mar 2026 12:07:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w2pgn-00AJV4-1P for pgsql-docs@arkaria.postgresql.org; Wed, 18 Mar 2026 12:07:53 +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 1w2ouc-009sr5-2E for pgsql-docs@lists.postgresql.org; Wed, 18 Mar 2026 11:18:06 +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 1w2ouZ-00000000LUv-1il4 for pgsql-docs@lists.postgresql.org; Wed, 18 Mar 2026 11:18:05 +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=LyihJ81Gd0Apha9BgwQiePBkof+vJEkkMsuc+6M8f4Y=; b=k8D84NCT2gDMQQjYcY1OK3Diu2 vv4GWDSKK+xEIz0UEKr+Ng53SKITFOE2ONcmfovy/8Zc7+medXR1WmhGE/HbeLFUPm+RNoocnveAG rSdgMlV0nMHYahuqtHDLu+VjT2bmBPwqkBsXU60/U2MmX0RM61XxKfpSn585/xfSE9MeP3M8LAl8f xrPT2mAmFy0IOAZmCW/22gsVPVimWtlE2V3h0zle4qg0xbRiM39V3UHQv4uAuADT/uLKQAodjpYMB mwg7XRIbX7cB+hdwYNH4JWMdfhfkpXnA24FQ+9AE4c0f37DzQZm4+kyUQBTC/id5RO3f5TjBWYesF 5gB7IuIw==; 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 1w2oua-000yEx-1G for pgsql-docs@lists.postgresql.org; Wed, 18 Mar 2026 11:18: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 1w2ouZ-003w9y-1B for pgsql-docs@lists.postgresql.org; Wed, 18 Mar 2026 11:18:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Conflict in documentation To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: sebastian.blaziak@fisglobal.com Reply-To: sebastian.blaziak@fisglobal.com, pgsql-docs@lists.postgresql.org Date: Wed, 18 Mar 2026 11:17:10 +0000 Message-ID: <177383263022.811.383346008182718806@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-row-filter.html Description: On page https://www.postgresql.org/docs/current/logical-replication-row-filter.html= #LOGICAL-REPLICATION-ROW-FILTER-INITIAL-DATA-SYNC If the subscription requires copying pre-existing table data and a publication contains WHERE clauses, only data that satisfies the row filter expressions is copied to the subscriber. and Warning Because initial data synchronization does not take into account the publish parameter when copying existing table data, some rows may be copied that would not be replicated using DML. Refer to Section 29.9.1, and see Section 29.2.2 for examples. conflict.