public inbox for [email protected]  

help / color / mirror / Atom feed

From: David G. Johnston <[email protected]>
To: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Conflict in documentation
Date: Wed, 18 Mar 2026 07:14:49 -0700
Message-ID: <CAKFQuwau0rzpyGP7ww3uO=gu9wPZHEe2RVC-b70oxC4LrihrrA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Wednesday, March 18, 2026, PG Doc comments form <[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
> 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.

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: <CAKFQuwau0rzpyGP7ww3uO=gu9wPZHEe2RVC-b70oxC4LrihrrA@mail.gmail.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