You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
148107: sql: prevent backref leak on self-referencing triggers r=spilchen a=spilchen
Prior to this change, dropping a trigger on a table that had a self-referencing foreign key could leave a dangling back-reference to the table itself. This incorrect dependency caused DROP TABLE/SCHEMA/DATABASE to loop indefinitely.
During depedency cleanup of DROP TRIGGER, we omit FKs when collecting the forward references. FKs can safely be omitted because they aren't tracked in the DependedOnBy relationship. They have thier own separate tracking in the table descriptor.
Fixes#147981
Epic: none
Release note: none
Note: omitting a bug-fix release note because this is a problem only on master.
Co-authored-by: Matt Spilchen <[email protected]>
0 commit comments