public inbox for [email protected]
help / color / mirror / Atom feedFrom: Blaziak, Sebastian <[email protected]>
To: David G. Johnston <[email protected]>
To: [email protected] <[email protected]>
Subject: RE: Conflict in documentation
Date: Wed, 18 Mar 2026 14:55:02 +0000
Message-ID: <VI0PR08MB10512BF815525F86DB76287B5EE4EA@VI0PR08MB10512.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAKFQuwau0rzpyGP7ww3uO=gu9wPZHEe2RVC-b70oxC4LrihrrA@mail.gmail.com>
References: <[email protected]>
<CAKFQuwau0rzpyGP7ww3uO=gu9wPZHEe2RVC-b70oxC4LrihrrA@mail.gmail.com>
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 <[email protected]>
Sent: Wednesday, 18 March 2026 15:15
To: Blaziak, Sebastian <[email protected]>; [email protected]
Subject: Re: Conflict in documentation
On Wednesday, March 18, 2026, PG Doc comments form <[email protected]<mailto:[email protected]>> wrote:
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/logical-replication-row-filter.html<https://urldefense.com/v3/...;
Description:
On page
https://www.postgresql.org/docs/current/logical-replication-row-filter.html#LOGICAL-REPLICATION-ROW-...;
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.
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: RE: Conflict in documentation
In-Reply-To: <VI0PR08MB10512BF815525F86DB76287B5EE4EA@VI0PR08MB10512.eurprd08.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox