| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amitkapila16(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: Question Regarding Publication Membership and Inheritance |
| Date: | 2026-03-03 05:38:32 |
| Message-ID: | CAKFQuwYjz+=nrKcNbj2pWY7Toszb1eqO1rMAFQqcHsPFOmjoHQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, March 2, 2026, shveta malik <shveta(dot)malik(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-03-03 05:51:23 | Re: doc: Clarify that empty COMMENT string removes the comment |
| Previous Message | Michael Paquier | 2026-03-03 05:36:50 | Re: Add expressions to pg_restore_extended_stats() |