| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Blaziak, Sebastian" <sebastian(dot)blaziak(at)fisglobal(dot)com> |
| Cc: | PostgreSQL Documentation <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Conflict in documentation |
| Date: | 2026-03-18 16:55:39 |
| Message-ID: | CAKFQuwaaCE42a3Of_Lt5QUgZ2rPEhu2ft_3ASXvnyc1Di2i+ag@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Mar 18, 2026, 07:55 Blaziak, Sebastian <
sebastian(dot)blaziak(at)fisglobal(dot)com> wrote:
> 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.
>
>
"publish" is a setting, it is completely orthogonal to the ability to
specify a "where" clause.
A where clause is always applied, both for the transfer of the ledger table
data and the transfer of journal event data. The publish setting can only
ever apply to the transfer of journal event data by its very nature.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Fittl | 2026-03-18 22:10:34 | Re: pg_stat_statements does not require shared_preload_libraries to be modified |
| Previous Message | Blaziak, Sebastian | 2026-03-18 14:55:02 | RE: Conflict in documentation |