Re: Segmentation fault during update inside ExecBRUpdateTriggers

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Andres Freund <andres@anarazel.de>

Cc: Thomas Munro <thomas.munro@gmail.com>, Piotr Gabriel Kosinski <pg.kosinski@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

Date: 2019-08-15T23:39:05Z

Lists: pgsql-bugs

Andres Freund <andres@anarazel.de> writes:
> There's
> commit 25b692568f429436f89ff203c1413e9670d0ad67

> But that shouldn't itself have caused it. But the referenced 4b93f5799
> might have.

Yeah, the problem is that that fix didn't fully close the hole.

			regards, tom lane

Commits

Prevent possible double-free when update trigger returns old tuple.
- cb0c79ae6231 9.5.20 landed
- afa71d9152a2 9.4.25 landed
- aed967d697de 11.6 landed
- 60886965a271 10.11 landed
- 1fe8d209ed84 9.6.16 landed
- 1ced082b95b3 13.0 landed
- 03813a50efa5 12.0 landed
Prevent dangling-pointer access when update trigger returns old tuple.
- 25b692568f42 11.0 cited