Re: Segmentation fault during update inside ExecBRUpdateTriggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Piotr Gabriel Kosinski <pg(dot)kosinski(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Segmentation fault during update inside ExecBRUpdateTriggers
Date: 2019-08-15 23:39:05
Message-ID: 12922.1565912345@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> There's
> commit 25b692568f429436f89ff203c1413e9670d0ad67

> But that shouldn't itself have caused it. But the referenced 4b93f5799
> might have.

Yeah, the problem is that that fix didn't fully close the hole.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-08-16 00:05:20 Re: Segmentation fault during update inside ExecBRUpdateTriggers
Previous Message Thomas Munro 2019-08-15 23:35:39 Re: Segmentation fault during update inside ExecBRUpdateTriggers