From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables |
Date: | 2020-04-08 16:50:45 |
Message-ID: | 1012.1586364645@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Hmm. Let's agree to what behavior we want, and then we implement that.
> It seems to me there are two choices:
> 1. on detach, keep the trigger but make it independent of the trigger on
> parent. (This requires that the trigger is made dependent on the
> trigger on parent, if the table is attached as partition again;
> otherwise you'd end up with multiple copies of the trigger if you
> detach/attach multiple times).
> 2. on detach, remove the trigger from the partition.
> I think (2) is easier to implement, but (1) is the more convenient
> behavior.
I think that #1 would soon lead to needing all the same infrastructure
as we have for inherited columns and constraints, ie triggers would need
equivalents of attislocal and attinhcount. I don't really want to go
there, so I'd vote for #2.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2020-04-08 16:56:53 | doc review for v13 |
Previous Message | Justin Pryzby | 2020-04-08 16:44:33 | Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables |