MIME-Version: 1.0
References: <CAFCRh--VRAHh2D7PsvW1mgRFfx2bqLQH_8asEBTLBn3RDLT7tA@mail.gmail.com>
 <185dd861-4e5a-47c0-9f2e-84dfa8a406ca@postgrespro.ru>
In-Reply-To: <185dd861-4e5a-47c0-9f2e-84dfa8a406ca@postgrespro.ru>
From: Dominique Devienne <ddevienne@gmail.com>
Date: Mon, 25 Aug 2025 19:24:06 +0200
Message-ID: <CAFCRh-85iWNy51sQBiVtwE=xq_pEhqR_cOetTa0-DK9TCjqQyw@mail.gmail.com>
Subject: Re: DISABLE TRIGGER doc wrong?
To: Pavel Luzanov <p.luzanov@postgrespro.ru>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAFCRh-85iWNy51sQBiVtwE%3Dxq_pEhqR_cOetTa0-DK9TCjqQyw%40mail.gmail.com>
Precedence: bulk

On Mon, Aug 25, 2025 at 7:13=E2=80=AFPM Pavel Luzanov <p.luzanov@postgrespr=
o.ru> wrote:
> On 25.08.2025 19:19, Dominique Devienne wrote:
> Simple experiment shows that it is still up to date:

> alice@postgres(17.5)=3D> alter table t disable trigger "RI_ConstraintTrig=
ger_a_1260370";
> ERROR:  permission denied: "RI_ConstraintTrigger_a_1260370" is a system t=
rigger
> alice@postgres(17.5)=3D> \c - postgres
> You are now connected to database "postgres" as user "postgres".
> postgres@postgres(17.5)=3D# alter table t disable trigger "RI_ConstraintT=
rigger_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 =3D=3D USER, implicitly? If that's the case, then the
doc still needs clarifications IMHO. --DD