On Monday, March 2, 2026, shveta malik <[email protected]> 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. 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 pertaining to ONLY says what this does and never communicates that future inherit-based interactions come into play. We tend not to describe things that don’t happen, and the lack of reported user confusion doesn’t support making an exception here. But a concrete suggestion could be considered. David J.
