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

From Andreas Joseph Krogh
Subject Re: Segmentation fault with PG-12
Date
Msg-id VisenaEmail.1.b1a37a733981955c.16db7338215@tc7-visena
Whole thread Raw
In response to Re: Segmentation fault with PG-12  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
På torsdag 10. oktober 2019 kl. 21:32:38, skrev Tom Lane <tgl@sss.pgh.pa.us>:
Andres Freund <andres@anarazel.de> writes:
> On 2019-10-09 10:16:37 -0400, Tom Lane wrote:
>> 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.

Bingo.  I can reproduce the crash (using concurrent updates of the same
table row, in the schema Andreas sent off-list) on the predecessor of
that commit, but on that commit it's fine.
 
 
That's great!
 
 
Andreas, that's a pretty simple patch if you're in a position to
build from source ...

regards, tom lane
 
 
Yes, we've built a new .deb-package from f224c7c11ea7be2751e3342e11317070ffb5622d in REL_12_STABLE which we'll deploy tonight.
Thanks!
 
--
Andreas Joseph Krogh

pgsql-general by date:

Previous
From: Yessica Brinkmann
Date:
Subject: Re: The connection to the server was lost. Attempting reset: Failed.
Next
From: pascal.crozet
Date:
Subject: Re: plpgsql copy import csv double quotes