Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: ahodgson(at)simkin(dot)ca, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
Date: 2023-03-03 15:50:40
Message-ID: 2473213.1677858640@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> I can throw together a patch for what I was thinking of.

Basically just make the recursive steps match on tgparentid instead
of name, like this.

I wonder whether anyplace else is making a similar mistake? Although
there's not much we will let you do to a foreign key trigger, so it
might not matter for anything else.

regards, tom lane

Attachment Content-Type Size
fix-bug-17817.patch text/x-diff 6.4 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2023-03-03 18:17:35 Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
Previous Message Tom Lane 2023-03-03 14:47:11 Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails