Обсуждение: Conflict in documentation
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.
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.
Hi David
The first line states that the initial data copy will _only_ copy filtered / relevant data.
While warning, but also elsewhere in the documentation it is stated that initial table _does not_ respect any publish limitations.
Hence the conflict.
Thx
Seb
From: David G. Johnston <david.g.johnston@gmail.com>
Sent: Wednesday, 18 March 2026 15:15
To: Blaziak, Sebastian <sebastian.blaziak@fisglobal.com>; pgsql-docs@lists.postgresql.org
Subject: Re: Conflict in documentation
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 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.
Hi David
The first line states that the initial data copy will _only_ copy filtered / relevant data.
While warning, but also elsewhere in the documentation it is stated that initial table _does not_ respect any publish limitations.
Hence the conflict.