MIME-Version: 1.0
References: <177383263022.811.383346008182718806@wrigleys.postgresql.org>
 <CAKFQuwau0rzpyGP7ww3uO=gu9wPZHEe2RVC-b70oxC4LrihrrA@mail.gmail.com>
 <VI0PR08MB10512BF815525F86DB76287B5EE4EA@VI0PR08MB10512.eurprd08.prod.outlook.com>
In-Reply-To: 
 <VI0PR08MB10512BF815525F86DB76287B5EE4EA@VI0PR08MB10512.eurprd08.prod.outlook.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 18 Mar 2026 09:55:39 -0700
Message-ID: 
 <CAKFQuwaaCE42a3Of_Lt5QUgZ2rPEhu2ft_3ASXvnyc1Di2i+ag@mail.gmail.com>
Subject: Re: Conflict in documentation
To: "Blaziak, Sebastian" <sebastian.blaziak@fisglobal.com>
Cc: PostgreSQL Documentation <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000e9f96e064d4f5266"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwaaCE42a3Of_Lt5QUgZ2rPEhu2ft_3ASXvnyc1Di2i%2Bag%40mail.gmail.com>
Precedence: bulk

--000000000000e9f96e064d4f5266
Content-Type: text/plain; charset="UTF-8"

On Wed, Mar 18, 2026, 07:55 Blaziak, Sebastian <
sebastian.blaziak@fisglobal.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.

--000000000000e9f96e064d4f5266
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><br><br><div class=3D"gmail_quote gmail_quote_container" =
dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar 18, 2026, 07=
:55 Blaziak, Sebastian &lt;<a href=3D"mailto:sebastian.blaziak@fisglobal.co=
m">sebastian.blaziak@fisglobal.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">


<div lang=3D"en-BE" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:break=
-word">
<div class=3D"m_4417783293301955026WordSection1">
<p class=3D"MsoNormal"><span>Hi David<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span>The first line states that the initial data co=
py will _<i>only</i>_ copy filtered / relevant data.<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span>While warning, but also elsewhere in the docum=
entation it is stated that initial table _<i>does not</i>_ respect any publ=
ish limitations.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span>Hence the conflict.<u></u><u></u></span></p>
<p class=3D"MsoNormal"></p></div></div></blockquote></div><div dir=3D"auto"=
><br></div><div dir=3D"auto">&quot;publish&quot; is a setting, it is comple=
tely orthogonal to the ability to specify a &quot;where&quot; clause.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">A where clause is always appl=
ied, both for the transfer of the ledger table data and the transfer of jou=
rnal event data.=C2=A0 The publish setting can only ever apply to the trans=
fer of journal event data by its very nature.</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">David J.</div><div dir=3D"auto"><br></div><div dir=3D=
"auto"><br></div></div>

--000000000000e9f96e064d4f5266--