| From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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>, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Subject: | Re: Question Regarding Publication Membership and Inheritance |
| Date: | 2026-03-03 11:54:14 |
| Message-ID: | CAJpy0uBw6KFW4iCf17GphSVBVo4wEXji19=_U9JYNsRq=dJNTQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 3, 2026 at 11:08 AM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> 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.
>
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 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-03-03 11:55:36 | Re: Cleanup shadows variable warnings, round 1 |
| Previous Message | Jakub Wartak | 2026-03-03 11:42:13 | Re: pg_plan_advice (now with transparent SQL plan performance overrides - pg_stash_advice) |