From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: backend crash on DELETE, reproducible locally |
Date: | 2018-11-01 15:43:56 |
Message-ID: | 18072.1541087036@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Ah, now this is interesting. Can you please supply the definition of
> the table? I'm wondering if there is a partitioned table with an FK to
> this one. I'm not quite seeing how come 'tup' is NULL there.
Yeah, apparently we've passed a null OLD tuple to an RI_FKey_cascade_del
trigger, which surely shouldn't happen. It'd be interesting to look at
the set of triggers on this table. I don't entirely trust psql's \d
to show us reality if there's something screwed up about the triggers,
so in addition to \d output, could we see
select * from pg_trigger where tgrelid = 'ref.auto_hint'::regclass;
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2018-11-01 15:51:49 | Re: backend crash on DELETE, reproducible locally |
Previous Message | Karsten Hilbert | 2018-11-01 15:41:13 | Re: backend crash on DELETE, reproducible locally |
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2018-11-01 15:51:49 | Re: backend crash on DELETE, reproducible locally |
Previous Message | Karsten Hilbert | 2018-11-01 15:41:13 | Re: backend crash on DELETE, reproducible locally |