From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Segmentation fault with PG-12 |
Date: | 2019-10-12 11:36:24 |
Message-ID: | VisenaEmail.15.c4570dd9ef6841fc.16dbfc04734@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
På torsdag 10. oktober 2019 kl. 22:21:13, skrev Andres Freund <
andres(at)anarazel(dot)de <mailto:andres(at)anarazel(dot)de>>:
On 2019-10-10 15:32:38 -0400, Tom Lane wrote:
> 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.
Cool, and thanks for checking.
No crashes in production after deploying the fix.
--
Andreas Joseph Krogh
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Moench-Tegeder | 2019-10-12 13:14:24 | Re: Perl DBI converts UTF-8 again to UTF-8 before sending it to the server |
Previous Message | Francisco Olarte | 2019-10-12 11:33:59 | Re: SELECT d02name::bytea FROM ... && DBI::Pg |