On 2025-Mar-26, Amul Sul wrote: > The reason for the change is to revert to the behavior before commit > #80d7f990496b1c, where recursion occurred regardless of the > changed flags. This is also described in the header comment for > ATExecAlterConstrDeferrability() (earlier it was for > ATExecAlterConstraintInternal): > > * Note that we must recurse even when the values are correct, in case > * indirect descendants have had their constraints altered locally. > * (This could be avoided if we forbade altering constraints in partitions > * but existing releases don't do that.)
Umm, why? Surely we should not allow a partition tree to become inconsistent. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ #error "Operator lives in the wrong universe" ("Use of cookies in real-time system development", M. Gleixner, M. Mc Guire)
