| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE: warn when actions do not recurse to partitions |
| Date: | 2026-01-12 14:40:00 |
| Message-ID: | CAKFQuwZXt2dAuHFs6MtRCzfMP6YZFzssuzdW2woJBVmco=CDdQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, January 12, 2026, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
> For now, I’ve limited the change to REPLICA IDENTITY to see whether there
> are objections to this approach. If there are none, I plan to extend the
> same warning behavior to the other sub-commands listed above. After that,
> users can reasonably assume that an ALTER TABLE partitioned_table
> ... action will recurse to child partitions unless a warning explicitly
> tells them otherwise.
>
It should be a notice, not a warning.
How about indicating how many partitions were affected in the notice and
allowing the absence of such a notice to be the indicator that cascading
did not happen?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2026-01-12 14:50:03 | Re: pg_plan_advice |
| Previous Message | Dilip Kumar | 2026-01-12 14:32:49 | Re: Proposal: Conflict log history table for Logical Replication |