| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 11:21:44 |
| Message-ID: | 20230303112144.tzw3yeos2c5w3q6y@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2023-Mar-01, Tom Lane wrote:
> Interestingly, although that commit was back-patched to v11, the failure
> does not occur in pre-v15 branches. So what's different about v15?
Hmm, I think f4566345cf40 probably explains that.
> It's a reasonable bet that we're trying to look up the child trigger
> using the name of its parent trigger ... but why are we searching by
> name at all, rather than OID? Seems mighty failure-prone.
I have no recollection of this, but we probably didn't have the OID
originally. It may be that simply changing that is enough to solve the
problem. I'll try to have a look later today, but I'm not sure I'll
have time.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-03 14:47:11 | Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails |
| Previous Message | Tom Lane | 2023-03-02 16:09:00 | Re: BUG #17819: The assert failed #17334 has not been repaired |