Re: Question Regarding Publication Membership and Inheritance - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Question Regarding Publication Membership and Inheritance
Date
Msg-id CAKFQuwYjz+=nrKcNbj2pWY7Toszb1eqO1rMAFQqcHsPFOmjoHQ@mail.gmail.com
Whole thread
In response to Question Regarding Publication Membership and Inheritance  (shveta malik <shveta.malik@gmail.com>)
Responses Re: Question Regarding Publication Membership and Inheritance
List pgsql-hackers
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.

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.

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add expressions to pg_restore_extended_stats()
Next
From: Fujii Masao
Date:
Subject: Re: doc: Clarify that empty COMMENT string removes the comment