| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Frederico Costa Galvão <frederico(dot)costa(dot)galvao(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, kanwei(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org> |
| Subject: | Re: BUG #15489: Segfault on DELETE |
| Date: | 2018-11-08 01:28:43 |
| Message-ID: | 22085.1541640523@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?UTF-8?Q?Frederico_Costa_Galv=c3=a3o?= <frederico(dot)costa(dot)galvao(at)gmail(dot)com> writes:
> I stumbled upon this issue yesterday, and trying to reduce and pinpoint
> it, I managed to get to this:
Yeah, this looks like the expand_tuple bug: you've got a foreign-key
trigger and a tuple that doesn't match the table rowtype anymore.
This example doesn't crash for me in HEAD or 11.1.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-11-08 01:33:39 | Re: BUG #15489: Segfault on DELETE |
| Previous Message | Frederico Costa Galvão | 2018-11-08 01:10:18 | Re: Re: BUG #15489: Segfault on DELETE |