On Mon, Aug 25, 2025 at 7:13 PM Pavel Luzanov <p.luzanov@xxxxxxxxxxxxxx> wrote: > On 25.08.2025 19:19, Dominique Devienne wrote: > Simple experiment shows that it is still up to date: > alice@postgres(17.5)=> alter table t disable trigger "RI_ConstraintTrigger_a_1260370"; > ERROR: permission denied: "RI_ConstraintTrigger_a_1260370" is a system trigger > alice@postgres(17.5)=> \c - postgres > You are now connected to database "postgres" as user "postgres". > postgres@postgres(17.5)=# alter table t disable trigger "RI_ConstraintTrigger_a_1260370"; > ALTER TABLE We were using ALL, successfully but incorrectly, and are now using USER, successfully. Not a named constraint trigger as you did. Could it be ALL implicitly excludes such constraint triggers, when not SUPERUSER? And thus, as the table owner, ALL == USER, implicitly? If that's the case, then the doc still needs clarifications IMHO. --DD
