public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dominique Devienne <[email protected]>
To: Pavel Luzanov <[email protected]>
Cc: [email protected]
Subject: Re: DISABLE TRIGGER doc wrong?
Date: Mon, 25 Aug 2025 19:24:06 +0200
Message-ID: <CAFCRh-85iWNy51sQBiVtwE=xq_pEhqR_cOetTa0-DK9TCjqQyw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAFCRh--VRAHh2D7PsvW1mgRFfx2bqLQH_8asEBTLBn3RDLT7tA@mail.gmail.com>
<[email protected]>
On Mon, Aug 25, 2025 at 7:13 PM Pavel Luzanov <[email protected]> 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
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: DISABLE TRIGGER doc wrong?
In-Reply-To: <CAFCRh-85iWNy51sQBiVtwE=xq_pEhqR_cOetTa0-DK9TCjqQyw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox