Re: Segmentation fault with PG-12

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Andreas Joseph Krogh <andreas(at)visena(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Segmentation fault with PG-12
Date: 2019-10-10 19:32:38
Message-ID: 22776.1570735958@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andres Freund <andres(at)anarazel(dot)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(at)anarazel(dot)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.

Andreas, that's a pretty simple patch if you're in a position to
build from source ...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Yessica Brinkmann 2019-10-10 19:43:52 Re: The connection to the server was lost. Attempting reset: Failed.
Previous Message Adrian Klaver 2019-10-10 19:20:15 Re: plpgsql copy import csv double quotes