| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "sebastian(dot)blaziak(at)fisglobal(dot)com" <sebastian(dot)blaziak(at)fisglobal(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Conflict in documentation |
| Date: | 2026-03-18 14:14:49 |
| Message-ID: | CAKFQuwau0rzpyGP7ww3uO=gu9wPZHEe2RVC-b70oxC4LrihrrA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wednesday, March 18, 2026, PG Doc comments form <noreply(at)postgresql(dot)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 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.
>
>
I don’t see a conflict.
But I also don’t 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’t make sense.
It’s 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’t do.
That all said I’m not planning on trying to push for a change here.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Blaziak, Sebastian | 2026-03-18 14:55:02 | RE: Conflict in documentation |
| Previous Message | PG Doc comments form | 2026-03-18 11:17:10 | Conflict in documentation |