MIME-Version: 1.0
In-Reply-To: <177383263022.811.383346008182718806@wrigleys.postgresql.org>
References: <177383263022.811.383346008182718806@wrigleys.postgresql.org>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 18 Mar 2026 07:14:49 -0700
Message-ID: 
 <CAKFQuwau0rzpyGP7ww3uO=gu9wPZHEe2RVC-b70oxC4LrihrrA@mail.gmail.com>
Subject: Re: Conflict in documentation
To: "sebastian.blaziak@fisglobal.com" <sebastian.blaziak@fisglobal.com>,
	"pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000378f91064d4d133b"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwau0rzpyGP7ww3uO%3Dgu9wPZHEe2RVC-b70oxC4LrihrrA%40mail.gmail.com>
Precedence: bulk

--000000000000378f91064d4d133b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, March 18, 2026, PG Doc comments form <noreply@postgresql.org>
wrote:

> 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 filt=
er
> expressions is copied to the subscriber.
>
> and
>
> Warning
> Because initial data synchronization does not take into account the publi=
sh
> 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 Secti=
on
> 29.2.2 for examples.
>
> conflict.
>
>
I don=E2=80=99t see a conflict.

But I also don=E2=80=99t really see the point of the warning - at least not=
 with
its present wording.  There is the initial state and the change log (DML)
and comparing the two in this manner doesn=E2=80=99t make sense.

It=E2=80=99s seems a bit heavy to say: warning - publish does not apply to =
the
initial table sync.  It seems like it could easily just be a note; or
removed altogether as we try to avoid documenting what things don=E2=80=99t=
 do.

That all said I=E2=80=99m not planning on trying to push for a change here.

David J.

--000000000000378f91064d4d133b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, March 18, 2026, PG Doc comments form &lt;<a href=3D"mailto:no=
reply@postgresql.org">noreply@postgresql.org</a>&gt; wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">The following documentation comment has been logged on t=
he website:<br>
<br>
Page: <a href=3D"https://www.postgresql.org/docs/18/logical-replication-row=
-filter.html" target=3D"_blank">https://www.postgresql.org/<wbr>docs/18/log=
ical-replication-<wbr>row-filter.html</a><br>
Description:<br>
<br>
On page<br>
<a href=3D"https://www.postgresql.org/docs/current/logical-replication-row-=
filter.html#LOGICAL-REPLICATION-ROW-FILTER-INITIAL-DATA-SYNC" target=3D"_bl=
ank">https://www.postgresql.org/<wbr>docs/current/logical-<wbr>replication-=
row-filter.html#<wbr>LOGICAL-REPLICATION-ROW-<wbr>FILTER-INITIAL-DATA-SYNC<=
/a><br>
<br>
If the subscription requires copying pre-existing table data and a<br>
publication contains WHERE clauses, only data that satisfies the row filter=
<br>
expressions is copied to the subscriber.<br>
<br>
and<br>
<br>
Warning<br>
Because initial data synchronization does not take into account the publish=
<br>
parameter when copying existing table data, some rows may be copied that<br=
>
would not be replicated using DML. Refer to Section 29.9.1, and see Section=
<br>
29.2.2 for examples.<br>
<br>
conflict.<br><br>
</blockquote><div><br></div><div>I don=E2=80=99t see a conflict.</div><div>=
<br></div><div>But I also don=E2=80=99t really see the point of the warning=
 - at least not with its present wording.=C2=A0 There is the initial state =
and the change log (DML) and comparing the two in this manner doesn=E2=80=
=99t make sense.</div><div><br></div><div>It=E2=80=99s seems a bit heavy to=
 say: warning - publish does not apply to the initial table sync.=C2=A0 It =
seems like it could easily just be a note; or removed altogether as we try =
to avoid documenting what things don=E2=80=99t do.</div><div><br></div><div=
>That all said I=E2=80=99m not planning on trying to push for a change here=
.</div><div><br></div><div>David J.</div><div><br></div>

--000000000000378f91064d4d133b--