From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jazz001319(at)gmail(dot)com |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17886: Error disabling user triggers on a partitioned table |
Date: | 2023-04-04 18:24:32 |
Message-ID: | 1582614.1680632672@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> result:
> postgres=# alter table public.test DISABLE TRIGGER USER;
> ERROR: 42704: trigger "trigger_test" for table "test_def" does not exist
> LOCATION: EnableDisableTriggerNew, trigger.c:1658
> Expected Result (Postgresql 15.2 and 14.4 - fine):
> testdb=> alter table public.test DISABLE TRIGGER USER;
> ALTER TABLE
Commit ec0925c22 seems to have been quite snakebit. I already fixed
a deficiency in it in v15/HEAD, but here we have a different symptom
in the older branches. What's happening is that EnableDisableTrigger
is ignoring the child trigger because it has tgisinternal set to true
and the command passes skip_system = true.
I'm inclined to think that in the older branches (pre f4566345c)
we need to do
- if (oldtrig->tgisinternal)
+ if (oldtrig->tgisinternal && !OidIsValid(oldtrig->tgparentid))
{
/* system trigger ... ok to process? */
but I've not tested that. Alvaro, what do you think?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2023-04-04 22:16:28 | Re: BUG #17885: slow planning constraint_exclusion |
Previous Message | jazzl 0013 | 2023-04-04 16:49:20 | Re: BUG #17886: Error disabling user triggers on a partitioned table |