Re: Segmentation fault during update inside ExecBRUpdateTriggers

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

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

To: Thomas Munro <thomas.munro@gmail.com>

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

Date: 2019-08-16T00:05:20Z

Lists: pgsql-bugs

Thomas Munro <thomas.munro@gmail.com> writes:
> 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 :-)

OK, pushed.

			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