| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:35:39 |
| Message-ID: | CA+hUKGKsgGvjmOR5mJ6dW07dEUfheuAjtCFdo=NAs88b+=TPGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Aug 16, 2019 at 11:26 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Ah, I see. I had written a test patch that uses plpgsql (attached for
posterity) but yours is better because it crashes more releases. I
will now get out of your way :-)
--
Thomas Munro
https://enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-double-free-when-one-trigger-passes-OLD-to-anoth.patch | application/octet-stream | 3.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-08-15 23:39:05 | Re: Segmentation fault during update inside ExecBRUpdateTriggers |
| Previous Message | Tom Lane | 2019-08-15 23:26:57 | Re: Segmentation fault during update inside ExecBRUpdateTriggers |