| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | 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:26:57 |
| Message-ID: | 12395.1565911617@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> [ thinks some more... ] Actually, I'm beginning to recall that
> we made changes here because v11 plpgsql is capable of actually
> returning "trigtuple" where before it would always have made a copy.
> If that's accurate, then very likely the bug exists further back
> but requires some other PL than plpgsql to manifest.
As I suspected ... the attached test case crashes 9.4 through 11.
We already had some problems in this area, which is why a suitable
trigger is already at hand in regress.c.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| test-for-trigger-troubles.patch | text/x-diff | 3.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2019-08-15 23:35:39 | Re: Segmentation fault during update inside ExecBRUpdateTriggers |
| Previous Message | Andres Freund | 2019-08-15 23:09:37 | Re: Segmentation fault during update inside ExecBRUpdateTriggers |