From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: DISABLE TRIGGER doc wrong? |
Date: | 2025-08-26 07:01:32 |
Message-ID: | CAFCRh-8hUbi26hfD5ev4A7UwNAOhnmHf-JFpsk0StTmvaFC=Yg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Aug 25, 2025 at 7:33 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 8/25/25 10:24, Dominique Devienne wrote:
> > On Mon, Aug 25, 2025 at 7:13 PM Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> wrote:
> >> On 25.08.2025 19:19, Dominique Devienne wrote:
> >> Simple experiment shows that it is still up to date:
Thanks Pavel. Indeed. See below.
> I am not seeing it:
Thanks Adrian. Indeed, it was my mistake.
I thought the 4 tables we had USER triggers on also had FKs, but I was mistaken.
I just tried on the 5th (and last) one we're adding triggers on, which
does have an FK, and I do get the documented (and verified by you
guys) error:
ERROR: permission denied: "RI_ConstraintTrigger_c_1226298044" is a
system trigger
(yes, that's a large OID... For a 1 year old DB)
I apologize for wasting your time. Thanks, --DD
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleas Mantzios | 2025-08-26 07:06:13 | Re: Strange deadlock with object/target of lock : transaction |
Previous Message | Laurenz Albe | 2025-08-26 06:22:42 | Re: Strange deadlock with object/target of lock : transaction |