On Tue, Mar 3, 2026 at 11:08 AM David G. Johnston
<david.g.johnston@gmail.com> wrote:
>
> On Monday, March 2, 2026, shveta malik <shveta.malik@gmail.com> wrote:
>>
>>
>> This is different from how partitioned tables behave. In the case of
>> partitioned tables, adding or removing a partition automatically
>> includes or excludes it from the publication.
>>
>> However, I would like to get feedback from others. Does this look like
>>
>> a bug, or is this the intended behavior?
>
>
> It’s defacto intended at this point.
>
Thanks for your feedback. That was my initial understanding as well.
>> Should we update the documentation to briefly mention that changes in
>> the inheritance tree are not reflected in the publication after its
>> creation unless done manually? Or is there a better approach?
>
>
> There is no bug in the existing documentation which corroborates this being the intended design. The commentary
pertainingto ONLY says what this does and never communicates that future inherit-based interactions come into play. We
tendnot to describe things that don’t happen, and the lack of reported user confusion doesn’t support making an
exceptionhere.
Okay, I see your point.
> But a concrete suggestion could be considered.
>
We could consider leaving it as is, given that we haven’t received any
user feedback suggesting a need to modify the documentation.
thanks
Shveta
