Postgres Pro
Downloads
Home   >   mailing lists

Re: FOR EACH ROW triggers, on partitioend tables, with indexes? - Mailing list pgsql-hackers

From David Rowley
Subject Re: FOR EACH ROW triggers, on partitioend tables, with indexes?
Date
Msg-id CAApHDvrmhE7eS2X2UQ0Rbcq7Z+3CU5NJUPamMsQrhxP=+4APhw@mail.gmail.com
Whole thread Raw
In response to Re: FOR EACH ROW triggers, on partitioend tables, with indexes?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Tree view 
On Thu, 1 Sept 2022 at 20:57, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> So apparently the way to get a trigger associated with a relation
> (tgconstrrelid) is via CREATE CONSTRAINT TRIGGER, but there doesn't
> appear to be a way to have it associated with a specific *index* on that
> relation (tgconstrindid).  So you're right that it appears to be dead
> code.
>
> If the regression tests don't break by removing it, I agree with doing
> that.

Thanks for having a look here. Yeah, it was a while ago.

I've pushed a patch to remove the dead code from master. I don't quite
see the sense in removing it in the back branches.

David

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Reducing the chunk header sizes on all memory context types
Next
From: "shiy.fnst@fujitsu.com"
Date:
Subject: RE: Handle infinite recursion in logical replication setup