| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Piotr Gabriel Kosinski <pg(dot)kosinski(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Segmentation fault during update inside ExecBRUpdateTriggers |
| Date: | 2019-08-15 23:09:37 |
| Message-ID: | 20190815230937.nazh3hp3o46vnk7n@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2019-08-15 18:39:24 -0400, Tom Lane wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > Right, this happens on REL_11_STABLE but not on master (which rewrote
> > the relevant code quite a bit in the "slotification" project).
>
> We should probably trace back why it doesn't happen before v11.
> I have a vague memory of having touched this code a year or two
> back, so likely this is my fault, but I wonder why it doesn't
> fail before.
There's
commit 25b692568f429436f89ff203c1413e9670d0ad67
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: 2018-02-27 13:27:38 -0500
Prevent dangling-pointer access when update trigger returns old tuple.
But that shouldn't itself have caused it. But the referenced 4b93f5799
might have.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-08-15 23:26:57 | Re: Segmentation fault during update inside ExecBRUpdateTriggers |
| Previous Message | Tom Lane | 2019-08-15 22:39:24 | Re: Segmentation fault during update inside ExecBRUpdateTriggers |