Re: Segmentation fault with PG-12 - Mailing list pgsql-general

From Andres Freund
Subject Re: Segmentation fault with PG-12
Date
Msg-id 877e5duq7t.fsf@alap4.lan
Whole thread Raw
In response to Re: Segmentation fault with PG-12  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Segmentation fault with PG-12
Re: Segmentation fault with PG-12
List pgsql-general
On 2019-10-09 10:16:37 -0400, Tom Lane wrote:
> Andreas Joseph Krogh <andreas@visena.com> writes:
> > Attached is output from "bt full". Is this helpful? 
> 
> Well, it shows that the failure is occurring while trying to evaluate
> a variable in a trigger's WHEN clause during
> "UPDATE origo_email_delivery SET folder_id=$1, created=$2\nWHERE entity_id IN ($3)\nRETURNING entity_id"
> And I'd bet that the root cause is something to do with Andres' tuple slot
> work.  But (at least to my eye) it's not apparent exactly what's wrong.

It looks like this could "just" be another report of #16036, which was
already fixed in:

commit d986d4e87f61c68f52c68ebc274960dc664b7b4e
Author: Andres Freund <andres@anarazel.de>
Date:   2019-10-04 11:59:34 -0700

    Fix crash caused by EPQ happening with a before update trigger present.


> This doesn't seem to correlate with your original report, btw,
> as that claimed the crash was during COMMIT.

That however, would be confusing, unless there's some deferred trigger
that causes another update, which then fires a before update trigger
causing the problem.

Greetings,

Andres Freund



pgsql-general by date:

Previous
From: Shankar Bhaskaran
Date:
Subject: Version 10.7 of postgres
Next
From: Michael Paquier
Date:
Subject: Re: Version 10.7 of postgres