Re: Segmentation fault during update inside ExecBRUpdateTriggers - Mailing list pgsql-bugs

From Andres Freund
Subject Re: Segmentation fault during update inside ExecBRUpdateTriggers
Date
Msg-id 20190815230937.nazh3hp3o46vnk7n@alap3.anarazel.de
Whole thread Raw
In response to Re: Segmentation fault during update inside ExecBRUpdateTriggers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Segmentation fault during update inside ExecBRUpdateTriggers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2019-08-15 18:39:24 -0400, Tom Lane wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > Right, this happens on REL_11_STABLE but not on master (which rewrote
> > the relevant code quite a bit in the "slotification" project).
> 
> We should probably trace back why it doesn't happen before v11.
> I have a vague memory of having touched this code a year or two
> back, so likely this is my fault, but I wonder why it doesn't
> fail before.

There's

commit 25b692568f429436f89ff203c1413e9670d0ad67
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   2018-02-27 13:27:38 -0500

    Prevent dangling-pointer access when update trigger returns old tuple.

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

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Segmentation fault during update inside ExecBRUpdateTriggers
Next
From: Tom Lane
Date:
Subject: Re: Segmentation fault during update inside ExecBRUpdateTriggers