Re: Segmentation fault with PG-12 - Mailing list pgsql-general
På onsdag 09. oktober 2019 kl. 16:16:37, skrev Tom Lane <tgl@sss.pgh.pa.us>:
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.
Can you show us the table definition and associated trigger definitions
for origo_email_delivery?
This doesn't seem to correlate with your original report, btw,
as that claimed the crash was during COMMIT.
regards, tom lane
FWIW: It doesn't always happen when that UPDATE-statement is issued, so it's not reproducable. We'll see what the next core-dump gives us.
Is it OK if I send you the table/trigger-definitions off-list?
-- 
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
Attachment
pgsql-general by date: