| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Segmentation fault with PG-12 |
| Date: | 2019-10-09 14:16:37 |
| Message-ID: | 21109.1570630597@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andreas Joseph Krogh <andreas(at)visena(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2019-10-09 14:36:19 | Re: Segmentation fault with PG-12 |
| Previous Message | Stephen Frost | 2019-10-09 13:31:22 | Re: GSSAPI: logging principal |